My projects
A set of tools, components and libraries that you can use in your project
Just think: if you could borrow one library, one function or even one method... that was the beginning of the toolkit - loose files with code that I could copy and paste into a new project.
The main repository is complemented by:
The php-js-css-web-toolkit repository contains libraries, components based on libraries and Composer packages, as well as development tools and various types of application backend workers.
Each library is independent of the other, as is each component. This principle ensures the portability of every tiny functionality within a specific commit (it's about the dependence of tools and components on specific revisions of libraries) - the project is not a monolith, but a collection of different libraries.
Documentation is not separate like in most projects - everything is described in libraries and tools (components are documented in README.md). You can transfer documentation with the code, and if you are not sure about something, you can take a look at the code (in most cases it is simple and readable).
Tools, when it makes sense (99% of cases) are interfaces between the terminal and the library/component. This approach provides the versatility of using the library/component from the command line and directly from the application.
The php-js-css-web-toolkit-extras repository contains additional tools, libraries with viral licenses, as well as those that are violent and vulgar.
The php-js-css-web-toolkit-app repository contains a sample application, on which you can test the entire project. After removing the samples (app/bin/remove-samples.php), you will get a skeleton: a few tools, components and a few libraries (facades). The skeleton does not limit you to specific design solutions - change whatever you want.
There's a lot of code, it's impossible to describe it all here. For more information, see the HOWTO.md file from the php-js-css-web-toolkit-app repository.
I have mirrors of my repositories on my server, so I decided to use that and disconnect from GitHub.
I'm not convinced about the new version of GitList, the P3X's version is not what I was looking for.
The legacy version is almost suitable but there are a few things missing.
I added them in this project.
The app was created for fun, after a long time of inactivity I improved the project to match what I implemented in Simpleblog.
In addition to the default modules and templates, the following are available:
If you use Git, you can add the above repositories as submodules.
If you are creating your small website or blog like this one, where you don't need to post hot breaking news, and you know how to code, there is no point in using PHP/WordPress/Joomla/etc.
But remember - servers are fast today.
If you care about time, use CMS.
I had a project to do and decided to use a virtual machine. It took me way too long to install and configure the system.
The idea was simple - you run a script on a freshly installed Debian, go to eat lunch/dinner and after eating you can start working.
All packages to be installed are listed in the file header.
The following tools were created for this project (you can use them without build-dev-env.sh):
README.md will look like in GitList and on GitHub
debootstrap-quick.pl bullseyebootstrap-installer-v2 package
If you want to automate the Debian installation process, use bootstrap-installer-v2 from the Debian router project.
I came up with the idea of my own server after my our Edimax WiFi access point stopped working due to the power supply. Initially, such an AP was a Compaq Armada E500 with Tiny7 (very slow boot) and then with Debian. The problem with this equipment was that it was difficult to manage: strange drivers for the WiFi card, and the card itself fell apart in the hands.
I decided to build a decent server on older but decent components. With tiny steps, I built the machine I had in mind:
The project has been divided into packages. Each of them has its own task:
misc package and desktop-toolbox extras
debootstrap-quick.pl tool you will download the Debian bootstrap, with this tool you will install it, and the build-dev-env.sh script will prepare the dev environment, after which you can copy the disk image to as many virtual machines as you want
wiki.debian.org and outputs data in console
*tableshdparm settings
/etc/hosts builder for dnsmasq
/var/log to tmpfs and syncs them to disk on shutdown
/etc/init.d/networking start in the backgroundnotify-daemon-v2n seconds
/etc/rc.local for easier maintenance/etc/rc.local for shutdown runlevels
/etc/resolv.conf/etc/resolv.conf and guarding it/etc/dhcp/dhclient.conf.
The repository also contains portable app builders (something like AppImage):
sample Debian package configurations:
containers:
and tweaks for:
update-grub during kernel (un)install
/etc/adjfileAdditionally, you will find an environment for QEMU-based virtual machines, as well as a PXE server environment.
My experiments with docker, WordPress, Joomla and Nginx proxy.
In addition, several tools to facilitate management - they are installed by the build-dev-env.sh script, as well as temporary containers.
My first Linux distribution. It was based on Debian Lenny (back then Sid), and that theme stuck with me.
Using such an old distribution is not an option, and the new version of ROX looks different. It takes a bit more effort, but I like simple solutions.
So I automated the whole process: one click, re-login, and the good old memories come back.
Page about the cdlinux.pl distribution (in Polish)
The repository also contains the lost cdlinux-new theme for IceWM. It was on forum.cdlinux.pl, but this forum no longer exists, and the copy on the Web archive is useless.