-
-
Notifications
You must be signed in to change notification settings - Fork 132
sndev runs on codespaces #2214
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
base: master
Are you sure you want to change the base?
sndev runs on codespaces #2214
Conversation
added info tooltip for LNURL-auth button
Update LNURL-UI
fixed linting errors
…ntioned in the package-lock.json file.
removed extra padding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for figuring out how to do this, but the issue is about making this run in codespaces without having to manually do things.
I'm not sure how to do that, which is why the issue exists.
Well, you have to set the .env variables by yourself I suppose
you don't have to do it anymore, I updated the description please do check, just setting the .env variables and running ./sndev start should do, the check for codespaces environment is set in the file I changed |
There should be some way of auto-exporting those env variables. The goal is one-click dev environments for contributors. If you can't figure it out, that's fine. If it's not possible, I'd appreciate linking to somewhere I can confirm it's not possible. |
Description
Closes #2209
Github Codespaces uses docker to run the platform like sndev. So this was a docker-in-docker error. Thus it was required to check explicitly if Docker was available in the codespaces.
Steps to run sndev on Github Codespaces:
npm install
. let it be finished.env
setbecause when I ran
docker ps -a && docker-compose ps && ./sndev status
it returned
because
opensearch
was not able to run as a healthy container./sndev start
. let it build and deploy the container, you should be able to see the containers icon appear in the sidebarwait for about 5 minutes or split terminal and/or check sndev status.
go to PORTS and open port 3000 on the web browser through the link from github codespaces (the browser icon that appears when you hover over port 3000) not from
http://localhost:3000
you will be able to see the live site on the page
Screenshots
Additional Context
Make sure the codespaces machine is the 8GB RAM and 32 GB storage one because running sndev puts great load on the CPU
Troubleshooting:
./sndev stop
and then./sndev start
again, there might be some image creation or memory failure- "_JAVA_OPTIONS=-Xms1g -Xmx1g -XX:UseSVE=0"
which is applicable for <=4GB RAM (even if you use the better machine in codespaces, this might help) indocker-compose.yml
(replace line 183)Checklist
Are your changes backwards compatible? Please answer below:
yup
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
10
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
N/A
Did you introduce any new environment variables? If so, call them out explicitly here: