it makes sense to have microvms available within lan. For example a microvm could run a cups print server to advertise our printer to computers in the network.
If we want microvms to be able to be accessed from the local area network of malobeo we have three options:
we port forward traffic from fanny to the vm
we give some vms ip addresses within the lan
we give all vms ip addresses within the lan
workarounds can be just running the services directly on fanny for now.
it makes sense to have microvms available within lan. For example a microvm could run a cups print server to advertise our printer to computers in the network.
If we want microvms to be able to be accessed from the local area network of malobeo we have three options:
- we port forward traffic from fanny to the vm
- we give some vms ip addresses within the lan
- we give all vms ip addresses within the lan
workarounds can be just running the services directly on fanny for now.
This may neccessary for running the zineshop iam working on: https://git.dynamicdiscord.de/kalipso/zineshop
This will require connection to the printer
Port-forwarding would probably be the easiest option but if we give some (all) vms their own ips we could setup dns to access services which is nicer than remembering port numbers.
Port-forwarding would probably be the easiest option but if we give some (all) vms their own ips we could setup dns to access services which is nicer than remembering port numbers.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
it makes sense to have microvms available within lan. For example a microvm could run a cups print server to advertise our printer to computers in the network.
If we want microvms to be able to be accessed from the local area network of malobeo we have three options:
workarounds can be just running the services directly on fanny for now.
This may neccessary for running the zineshop iam working on: https://git.dynamicdiscord.de/kalipso/zineshop
This will require connection to the printer
Port-forwarding would probably be the easiest option but if we give some (all) vms their own ips we could setup dns to access services which is nicer than remembering port numbers.
Alternatively set up a webpage on root to link to all other services
EDIT: Or a reverse proxy