TARDIS Project

User Tools

Site Tools

Trace:
howto:webapp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
howto:webapp [2023/07/29 11:20] – tcmalhowto:webapp [2025/03/29 07:13] (current) – [Keeping it running] merlin
Line 33: Line 33:
 Now you've gotten everything running within the network, it's time to put it on the internet! Before you do this, make an effort to check for any security holes or things that should only be exposed for development. Now you've gotten everything running within the network, it's time to put it on the internet! Before you do this, make an effort to check for any security holes or things that should only be exposed for development.
  
-Now, head to the [[https://console.tardisproject.uk|Tardis console]] and hit ''Manage endpoints''. An endpoint is just a forwarding from our publicly-accessible server, to an application inside the network. +Now, head to the [[https://console.tardisproject.uk|Tardis console]] and hit ''Endpoints''. An endpoint is just a forwarding from our publicly-accessible server, to an application inside the network. 
  
 You can create a new endpoint with your domain and whatever prefix you'd like. The target IP address will be ''192.168.0.130'' (the internal ip of the sandbox vm), and the target port will be whatever you set your application up to listen to. You can create a new endpoint with your domain and whatever prefix you'd like. The target IP address will be ''192.168.0.130'' (the internal ip of the sandbox vm), and the target port will be whatever you set your application up to listen to.
 +
 +If you want to use a custom domain, [[https://tardisproject.uk/chat|let an admin know]] and they'll set it up for you.
  
 === Endpoint options === === Endpoint options ===
 +
 +There are a couple of advanced options. In most cases you won't need to touch them, but if you have problems you should take a look.
  
 In most cases, you won't need to use HTTPs from the proxy to the target. You can test this by running ''curl localhost:<port>'' on the sandbox vm - if it succeeds then you don't need it. In most cases, you won't need to use HTTPs from the proxy to the target. You can test this by running ''curl localhost:<port>'' on the sandbox vm - if it succeeds then you don't need it.
Line 72: Line 76:
   - Hit ''Ctrl+b'', then ''d''. You'll go back to your original terminal, and see a message like ''[detached (from session 0)]''   - Hit ''Ctrl+b'', then ''d''. You'll go back to your original terminal, and see a message like ''[detached (from session 0)]''
  
-Your app is now running in the background - feel free to log out and it will stay running. If you want to get back to it to see logs or stop it, run ''tmux attach'' whenever you want.+Your app is now running in the background - feel free to log out and it will stay running. If you want to get back to it to see logs or stop it, run ''tmux attach'' whenever you want. However, if we restart the sandbox VM, which may happen due to maintenance, your app will not start back up.
  
 === Systemd === === Systemd ===
howto/webapp.1690629611.txt.gz · Last modified: 2023/07/29 11:20 by tcmal