Ooh, nice. GitLab CI actually lets you do interesting tests... Ones really requiring root. I'm surprised this didn't error: gitlab.com/derobert/aban/-/jobs/418300336
That message is printed when the beginning of the sexp is not visible in the window; otherwise, the opening paren is temporarily highlighted.
This behavior is implemented in simple.el and is not associated with any minor mode. It is implemented using a hook that runs when a character is inserte...
I want this too, but how do I make it not temporary? I.e. I want the message to stay in the minibuffer till the cursor is moved. — Faheem Mitha45 secs ago
Does anyone know what "Quick Backup through Solus". I need to back up my VPS instance, before reinstalling with an new Debian 10 kernel. But how does this compare to something like fsarchiver?
> We could provide some temporary space, yes. You could take a Quick Backup through Solus, we could copy that out, you could reinstall, and we could copy it back in. The kernel version is dependent on the node itself, so after the migration your server will reflect the newer kernel version.
@derobert you could run commands requireing root. Is it because you run them in a docker container? Does a docker container allow anyone to run commands requiring root?
Does Gitlab allow you to run an interactive shell to test and deploy your application for free?
@jesse_b I'm expecting to get a letter in the mail any year now calling me to my first free check. Then it's every X years (I don't remember what X is).
@StephenKitt yeah, you're (you==people raised as bilinguals) are unlikely to mix up such basic words. I'm quite capable of creating words like "floé" (from the English "flow" and the Greek "roé"), but I don't think I'd ever mix up the words for and. Maybe between languages I am not a native speaker of...
@Tim It's because they're apparently running the container with the --privileged option. Normally a Docker container (w/o that option) has limited root access, to affect only things inside the container. But not global things like loop devices and device-mapper.
@Tim They offer free runners (which aren't interactive, but basically run shell scripts for you) for free to open source projects.
@Tim docs.gitlab.com/ee/ci/quick_start gives an example script to get one running. You can ignore the parts about setting up runners if you're using gitlab.com (as they've already done that; those parts are only relevant if you're self-hosting gitlab)
Asking Google for gitlab ci tutorial also gave me a few videos, if that's what you prefer.
@Tim not sure if I've posted that particular link, but I think it's helpful to play with it to learn. And just using the GitLab.com setup will save you from all the sysadmin work installing it, setting up runners, etc.