Toolbox: using Silverblue for development - Debarshi Ray - Flock 2019

Fedora Silverblue is the next-generation Fedora Workstation that promises painless upgrades, clear separation between the OS and applications, and secure and cross-platform applications. The basic operating system is an immutable OSTree image, and all the applications are Flatpaks.
This talk is about taking a look at how to set up a development environment on this locked down operating system - how to install your favourite tools, editors and SDKs without DNF. It's going to focus on Toolbox and what it offers to support this use-case.
--
Recordings of talks at Flock are a community effort. Unfortunately not everything works perfectly every time. If you're interested in helping us improve, let us know.
🖥️ Download your favorite Fedora version now:
fedoraproject.org/

[@spaceiswater6539]

Thank you so much in showing us what the toolbox does.

[@yuriykazmirchuk9641]

Very exciting! Keep moving forward 😎👍

[@thiagosantos41]

Thanks! It's awesome tool for development.

[@marcello4258]

super interesting I think this might make my switch to Fedora.. this is pretty compelling.. I am wondering if you can manage several pods here?

[@spaceiswater6539]

I tried SilverBlue and really liked it the only gripe I have is that you can't search the repo's using the rpm-ostree as you can with dnf, dnf search 'software name' as there seems to be no 'search' option using rpm-ostree, so what I had to do was create a toolbox then do a dnf search on that then find the repo software name then use rpm-ostree to install it, has anyone else had this problem?

[@UpcycleElectronics]

I've seen issues. Like after adding mlocate via rpm-ostree, _locate_ doesn't work. I'm probably doing something wrong. In the past I had to use:
$ updatedb
...on Ubuntu to get _locate_ to work correctly. I'm not sure if it needs something else to 'startdb' or whatever. It just doesn't work for me on Silverblue after adding and updating. Strace works though.
I try to run everything I can inside a toolbox. Just use aliases in .bashrc to make it easy to get in and out of toolboxes.
Also, inside your .bashrc add:
if [[ $PS1 == *""* ]] ; then
This will give you a space to make specific commands do different things in the main shell versus a toolbox shell.
Another big help for me has been adding:
function bash(){
command history -a
command bash
}
...to my .bashrc. That keeps my command history persistent in the toolbox.
Last .bashrc mod I'll mention is:
function toolbox() {
if [[ "$@" == *"stop "* ]] ; then
podman stop -a >> /dev/null
toolbox list
else
toolbox "$@"
fi
}
That just adds a way to stop a running container with the command:
$ toolbox stop

[@HaiNguyen-cf1ji]

Awesome, the tool work exactly the way I want it to :)) but it lack a good name, like there was the guy told me about toolbox but I'm like what toolbox he talking about, searching toolbox alone doesn't give any result only some Minecraft toolbox
Edit: you forgot to demo running emacs in toolbox