-
Notifications
You must be signed in to change notification settings - Fork 122
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
[Readme Request] Add documentation on how to self host manually #2
Comments
i simple way to do it can be to .. fork the server repo... use that repo to host a server on heroku |
and it would be convenient if would add a documentation for non power users or so.... |
I ended up using a light dedicated server I had, added the listen together on there, created a reverse proxy with Apache and used Certbot to give it https. Just add that code to a .conf in /etc/apache2/sites-available, change the "servername" and "name" with your own site name of choice, a2ensite it and then let certbot do it's thing enabling the https. If you are using a subdomain, then don't forget to make an A record of your subdomain in your provider of choice, I did this in Namecheap. As for Heroku, it would not allow me to even start the server up due to that salesforce policy error that keeps coming up I then tried raleway.app but the dropouts were so frequent that it was unusable. Only other thing that could be tried for non power users is possibly replit with an uptimerobot? Who knows... |
Would love to be able to host this separately onto a dedicated server as I attempted on Heroku and was told it goes against Salesforce's policy and trying Railway caused the connection to constantly drop. I'm not too sure how I would host this while I have an active domain and site available so any extra documentation for doing it manually and with my own domain would be greatly appreciated!
The text was updated successfully, but these errors were encountered: