fix activemaps_path url bug (#559)
* fix activemaps_path url bug * annoying doc updates * skip policy scope if redirecting an explore page * lol that would have been dumb
This commit is contained in:
parent
1f9078638e
commit
f5912d511d
2 changed files with 19 additions and 6 deletions
|
@ -39,7 +39,10 @@ class MapsController < ApplicationController
|
|||
|
||||
# GET /explore/mine
|
||||
def mymaps
|
||||
return redirect_to activemaps_url if !authenticated?
|
||||
if !authenticated?
|
||||
skip_policy_scope
|
||||
return redirect_to explore_active_path
|
||||
end
|
||||
|
||||
page = params[:page].present? ? params[:page] : 1
|
||||
@maps = policy_scope(
|
||||
|
@ -54,7 +57,10 @@ class MapsController < ApplicationController
|
|||
|
||||
# GET /explore/shared
|
||||
def sharedmaps
|
||||
return redirect_to activemaps_url if !authenticated?
|
||||
if !authenticated?
|
||||
skip_policy_scope
|
||||
return redirect_to explore_active_path
|
||||
end
|
||||
|
||||
page = params[:page].present? ? params[:page] : 1
|
||||
@maps = policy_scope(
|
||||
|
|
|
@ -47,10 +47,17 @@
|
|||
|
||||
Run this in the metamaps directory, still as metamaps:
|
||||
|
||||
# fill in DB_* values, and realtime server at least. Change the
|
||||
# SECRET_KEY_BASE to something new. Ctrl+X to save/exit from nano.
|
||||
cp .example-env .env
|
||||
nano .env # fill in DB_* values, and realtime server at least. Ctrl+X to save/exit.
|
||||
nano .env
|
||||
|
||||
# Set up environment variables in your current session
|
||||
source .env
|
||||
export RAILS_ENV=production
|
||||
rake db:setup #create, load schema, seed
|
||||
|
||||
# create, load schema, seed
|
||||
rake db:setup
|
||||
|
||||
Now set up nginx - config stored on Linode, including relevant environment
|
||||
variables.
|
||||
|
@ -61,8 +68,8 @@ Get an SSL certificate and encrypt it for the realtime video.
|
|||
|
||||
passenger-config restart-app /home/metamaps/metamaps
|
||||
|
||||
If this command fails, it may be helpful for debugging to run a test server to
|
||||
see what problems show up:
|
||||
If this command fails, it may be helpful for debugging to run a test
|
||||
server to see what problems show up:
|
||||
|
||||
RAILS_ENV=production rails server
|
||||
|
||||
|
|
Loading…
Reference in a new issue