forked from mattbillenstein/ve
-
Notifications
You must be signed in to change notification settings - Fork 1
The ve toolkit build system
License
omniprojects/ve
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
The ve toolkit Who: I'm Matt Billenstein -- I work mostly on backend systems supporting medium size web applications in Python. I love rsync. Why: I like OSS software, but one of the problems I've had is keeping a consistent set of tools around for use on both my development and production systems. The intention of this project is to stage all the common tooling into the same build prefix -- not relying too much on the underlying system packages gives us more control over which versions of each tool we use and when they get updated. What: This is a set of build scripts for compiling tools and libraries I use in building backend systems. It's intended as a way to keep these tools in sync across multiple hosts using rsync as well as supporting multiple operating systems and underlying package management systems. Currently, it supports recent Ubuntu LTS releases (16.04 / 18.04) and recent versions of MacOS (using homebrew), so it allows you to develop natively on MacOS or Ubuntu and deploy to Ubuntu using the same versions of all of these tools with a relatively small number of system shared-library dependencies. As of 03/16/2016 it contains: SION= pkgs/available/*.sh | sed -e 's/_VERSION=/ /g' -e 's/"//g' | awk '{printf "%-12s %25s\n", $1, $2}' | sort AIRFLOW 1.10.0 BEANSTALKD 1.10 CONSUL 0.6.3 DNSMASQ 2.79 GOLANG 1.9.2 GRAPHITE GITHUB_HEAD HAPROXY 1.8.13 MARIADB 10.1.13 MEMCACHED 1.5.10 METABASE 0.30.2 MONGODB 3.4.7 NODEJS 8.9.4 #NSQ 1.0.0-compat OPENRESTY 1.13.6.2 PERL 5.26.2 PGBOUNCER 1.8.1 PHANTOMJS 2.1.1 POSTGRES 9.6.10 PROTOBUF 3.5.1 PYPY v6.0.0 PYPY v6.0.0 PYTHON 2.7.15 PYTHON 3.6.6 REDIS 4.0.11 RUBY 2.4.4 SQUID 4.2-20180910-r6d8f397 VARNISH 4.1.10 YARN 1.9.4 Where: If you want to use this for real in any sort of production environment, you should fork this repo and build it yourself. Stage your own config_local.sh and optionally use a staging host to synchronize this between your systems via rsync and ssh (see push/pull.sh). Notes: I recommend using supervisord as your init for starting servers -- I plan to add example configs for these eventually. Many tools are built with options pointing what would typically be in /var on a system to /data. You'll need to create these directories manually with proper ownership to run many of the servers at the moment.
About
The ve toolkit build system
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- Shell 100.0%