Adding support for printers in different locations would be great. An idea would be that we have a central zineshop instance where print jobs get created for different printers. At each printers location a local host (pc, pi) would then periodically pull jobs for their location/printer using some api token.
This way these hosts dont need to face public internet and can sit easily behind nat/firewal.
Adding support for printers in different locations would be great. An idea would be that we have a central zineshop instance where print jobs get created for different printers. At each printers location a local host (pc, pi) would then periodically pull jobs for their location/printer using some api token.
This way these hosts dont need to face public internet and can sit easily behind nat/firewal.
When thinking about this it becomes obvious that a federated approach would be great, not only to print in different locations, but to share zine libaries. I will go a bit in evaluation but guess it is out of scope for this project since its architecture was never meant to run decentralized
When thinking about this it becomes obvious that a federated approach would be great, not only to print in different locations, but to share zine libaries. I will go a bit in evaluation but guess it is out of scope for this project since its architecture was never meant to run decentralized
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.
Adding support for printers in different locations would be great. An idea would be that we have a central zineshop instance where print jobs get created for different printers. At each printers location a local host (pc, pi) would then periodically pull jobs for their location/printer using some api token.
This way these hosts dont need to face public internet and can sit easily behind nat/firewal.
When thinking about this it becomes obvious that a federated approach would be great, not only to print in different locations, but to share zine libaries. I will go a bit in evaluation but guess it is out of scope for this project since its architecture was never meant to run decentralized