-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change where rooms frontend assets are served #56
Change where rooms frontend assets are served #56
Comments
@chereseeriepa planetary-social/go-ssb-room@5e2a2da I changed the way the assets are loaded. First we try to load So basically you should be able to move all your app files to Let me know if this works for you. |
Moved this back into this week as im unable to see the frontend in the dev room server
|
Ok for now I fixed the dev server to also serve assets from Do we also want to do the other requirement as part of this ticket ("by default, it should show the old UI when there is no web/app (its currently showing a list of the assets on the landing page instead") or is there a separate one for this? |
I just confirmed this is all working again and I will add
to separate card |
Need to change the location of where the frontend dist files are being served to make it easier for them to be replaced / overwritten by either manually (by someone) or automatic (through ansible)
The idea is that when someone creates a new production build of
rooms-frontend
(which each individual room will need to do in order to apply custom environment variables to therooms-frontend
), this change makes it a lot easier to overwrite the whole folder, rather than figuring out manually which ones need to be replaced/removed. This will then be a lot easier for the ansible script that will automate that process.Proposed solution:
go-ssb-room/web/assets
they are served atgo-ssb-room/web/assets/app
or something similarThe text was updated successfully, but these errors were encountered: