You have en option to install them automatically in the settings or per container
diminou
Just FYI cyberpunk works perfectly fine on Linux.
I understand the piracy, I'm not advocating it but I understand. But if you have the funds, and the company is worth getting your money why don't you just get out of all the trouble of finding how to play it and just buy it and play it without any issue?
With that said, lutris and/or bottle (or any other recent launcher to play video games on linux) will actually do the trick. If for some reason you are unable to find the how to somewhere I wonder if you should really be downloading executables off the internet. Even more so on windows if you are not using Linux anymore for ever.
Those are usually the vector of a lots of viruses and malwares.
Anyway. Have fun with cyberpunk, it's pretty great!... When you can launch it :-)
For printer it works out of the box you dont need any app.
For the MSI thingy.. Well there is multiple apps that can do that but truthfully you don't need to tweak as much as you do on windows, and if you do you'll find plethora of apps to help you achieve what you want
Oh I never knew either!
Not that you mention it it is true that I have not seen it update in a long time. Since I'm only using it from time to time and locally (mainly) I've never bothered to check.
What are you using instead?
Juicessh? One time payment, unfortunately not open source but can deal with a lot of services, you can use ssh key and I don't know what else you'd need but you can take a look (and test it for free since the payment is only to unlock features you might not need)
You are going to need a domain name and a reverse proxy. But to be honest of you are asking that kind of question means you should not make your instance public and advertise it to the world just yet.
Learn how to secure your infrastructure and how everything is working together first.
Then you can check out what a reverse proxy is and what it is used for.
Only then you can open your instance to the public with whatever services you'd like. But remember, opening it to the outside without any security knowledge is asking for trouble
Hello et joyeux Noël à tous !
J'ai reçu le kit de démarrage Donjons et chatons, et le jeu Let's summon demons. Deux jeux de société sur ma liste de souhaits de cette année ☺️
Tu ne pouvais pas utiliser ceux achetés il y a un an pour te déplacer ?
J'ai raté quelque chose dans le message ? 😅
You could probably go for nextcloud.yourdomain.ddns.org, but I can't guarantee that since I have no experience with ddns.org.
There is a lot of cheap registrars, I'll let you check and select the one you want if you need a second domain.
Basically docker let you setup multiple (fake) computers inside your computer. For those that want to correct this, I know. But I'm trying to explain the top view here.
So, your computer (host) is hosting multiple containers, each containers will have there set of available ports. And as stated earlier each container will have an application that may or may not need to expose ports. But since each have their own ports you can have hundreds of containers using the port 80 INSIDE the container, an using 8100 to 8200 OUTSIDE the container (on your host). The only real limit would be the amount of ports available (somewhere along the lines of 65535).
There. Now go have fun and read up on docker and reverse proxy! Don't forget to use ssl on your nextcloud instance since it'll be facing the internet! And.. Have fun! :-)
OK you are thinking at it the wrong way : 80 and 443 are the default ports for the web access of any web application.
You are using docker with the nextcloud aio image. Which mean, you are deploying a docker container which contain the web application.
What you are doing is using arbitrary ports for the container. This could be 7777. Then, this is redirected to 443 inside the container, to the web application.
This is why you can actually use any port you want for your container. You are not really switching the port for nextcloud, only for the container.
This is why I suggested doing 444:443 in the docker-compose.yml file: you are exposing 444 to the container, to 443 inside the container.
And this is why you can actually use any ports for every web app you are going to host : apache will redirect to the port you want to the container, a'd docker will redirect inside the container to either 80 or 443 (or anything else needed for that web application).
In fact 80 and 443 refer to http and https, those are default ports.
You can in fact use the ports you want for the service you want. I have multiple web services behind the ports 80 and 443, you need one service that is able to get the request at the correct port. This is the role of the reverse proxy.
Apache can assume that role, you go to anything.yourdomain.com and apache will then redirect "anything" to the correct service (with the internal ip and port). So say you want to put nextcloud at 7777 you can tell docker to expose 7777 and redirect it to 443 on nextcloud.
The chain is like that in the case : nextcloud.yourdomain.com > apache > nextcloud is at ip:7777 > redirect the request to 7777 > nextcloud homepage is shown
J'ai un chien problématique, elle refuse les rencontres et devient rapidement aggressive envers ses congénères.
J'ai adopté un chiot. Ils jouent ensemble comme si c'était les meilleurs amis.
Voilà. Ça va faire mes prochaines années ☺️