||3 weeks ago|
|install||3 weeks ago|
|packs||3 weeks ago|
|tools||1 month ago|
|uninstall||3 weeks ago|
|upgrade||3 weeks ago|
|.dockerignore||1 month ago|
|.editorconfig||3 weeks ago|
|.gitignore||1 month ago|
|Dockerfile||1 month ago|
|LICENSE||1 month ago|
|Makefile||3 weeks ago|
|README.md||1 month ago|
|gen-makefile||3 weeks ago|
My Ubuntu environment
make-ready bunch of scripts for easily installation of different software.
- Ubuntu >= 20.04 (not tested with version < 20)
make(optional but recommended)
wget(necessary for some scripts)
git(necessary for some scripts)
If some dependecies are missed for some of these scripts it is enougth to run
./install/apt in most cases.
Clone this repo (recommended)
# if git is installed git clone firstname.lastname@example.org:anthony/my-env.git --depth=1 # if git is not installed wget -qO - https://git.axenov.dev/anthony/my-env/archive/master.tar.gz | tar -zxf - # switch to repo dir cd my-env # generate fresh ./Makefile and get full list of `make` goals ./gen-makefile # get full list of `make` goals make help
I do not recommend to run
makewithout arguments since then ALL goals will be started in their order.
make helpto look around.
Selective straightforward installation
# from remote file wget -qO - https://git.axenov.dev/anthony/my-env/raw/branch/master/install/apt | bash # from locally cloned repo ./install/apt
How to add a new software script?
- Create new
At the beggining of a file you must write these two lines:
#!/bin/bash ##makedesc: Your description for Makefile
- Test your script
./gen-makefileto generate new
How to create packs?
You can create new file inside
Syntax is same as classic makefile with one important and necessary addition -- a comment started with
##mypack1: Pack description mypack1: goal1 goal2 goalX ... ... ##mypackX: Pack description mypackY: goalA goalB @cp file1 file2 ... ...
mypack*is the pack name
goal*are script names in
Testing in docker (not recommended)
Note that this is almost useless way to test since you'll meet errors in many cases because dockerized OS is not fully-functional and will never be.
You can use docker to test something really simple, e.g. to check general script steps or install cli tools.
In other cases you need virtualized Ubuntu instead of dockerized one, so I strongly recommend you to use VirtualBox or your host machine.
# switch to repo dir cd my-env # build and run container docker build -t myenv . && docker run -it myenv # or oneliner docker run -it $(docker build -q .)
Now you can play around with scripts.
- build: flameshot
- build: rustdesk
- JB mono (2)
- update scripts (when possible)
- uninstall scripts (when possible)