You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the patch to allow hosting a site from a non-root location (by adding vars to config.json). But now that I've done this, I can no longer do local testing, because URLs that used to be '/static/...' are now 'base_path/static/...' and so I can't test locally using cactus serve. Is there a work around I can use?
The text was updated successfully, but these errors were encountered:
@geomblog I have never used the patch you mentioned, and I don't know anything about it, but you could do something similar to the workaround that I reported in issue 273: First, remove the patch so that you can test locally using cactus serve. Then set up a test Amazon S3 bucket to which you can deploy. Then deploy to that test Amazon S3 bucket. Then use a separate client app (I use Cyberduck) to upload the contents of the local .deploy folder to whichever non-root location you want to use.
Thanks. Yes, that comment from 246 might be a useful workaround. The one involving S3 seems a little more involved (not to mention that I'd have to create an S3 bucket first).
I'm using the patch to allow hosting a site from a non-root location (by adding vars to config.json). But now that I've done this, I can no longer do local testing, because URLs that used to be '/static/...' are now 'base_path/static/...' and so I can't test locally using cactus serve. Is there a work around I can use?
The text was updated successfully, but these errors were encountered: