Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:

Last update: May 24, 2022
Salt Project License: Apache v2.0 PyPi Package Downloads PyPi Package Downloads Salt Project Slack Community Salt Project Twitch Channel Salt Project subreddit Follow SaltStack on Twitter
Salt Project Logo

Salt is the world’s fastest, most intelligent and scalable automation engine.

About Salt

Built on python, Salt uses simple and human-readable YAML combined with event-driven automation to deploy and configure complex IT systems. In addition to leveling-up vRealize Automation SaltStack Config, Salt can be found under the hood of products from Juniper, Cisco, Cloudflare, Nutanix, SUSE, and Tieto, to name a few.

About SaltStack

SaltStack was acquired by VMware in 2020. Salt Project remains an open source ecosystem that VMware supports and contributes to.

Download Salt

Salt is tested and packaged to run on CentOS, Debian, RHEL, Ubuntu, MacOS, Windows, and more. Download Salt and get started now.

Salt Project Documentation

Installation instructions, getting started guides, in-depth API documentation, and contributing to Salt.

Security Advisories

Keep an eye on the Salt Project Security Announcements landing page. Salt Project recommends subscribing to the Salt Project Security RSS feed to receive notification when new information is available regarding security announcements.

Other channels to receive security announcements include the Salt Community mailing list and the Salt Community Slack Channel.

Responsibly Reporting Security Vulnerabilities

When reporting security vulnerabilities for Salt or other SaltStack projects, refer to the SECURITY.md file found in this repository.

Engage the Salt Project and The Community

Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Project Community Events Calendar on the main https://saltproject.io website.

If you have additional questions, email us at [email protected] or reach out directly to the Community Manager, Janae Andrus via Slack. We’d be glad to have you join our community!

License

Salt is licensed under the Apache 2.0 license. Please see the LICENSE file for the full text of the Apache license, followed by a full summary of the licensing used by external modules.

A complete list of attributions and dependencies can be found here: salt/DEPENDENCIES.md

GitHub

https://github.com/saltstack/salt
Comments
  • 1. /tmp/salt-minions[BUG]

    Description My all servers with salt-minion installed,An unknown program suddenly ran today, He's /tmp/salt-minions

    [[email protected] ~]# top

    top - 10:06:44 up 511 days, 18:39, 3 users, load average: 2.01, 2.02, 1.91 Tasks: 193 total, 1 running, 192 sleeping, 0 stopped, 0 zombie Cpu(s): 7.2%us, 18.3%sy, 0.0%ni, 74.1%id, 0.4%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 8060948k total, 7502768k used, 558180k free, 76316k buffers Swap: 4194300k total, 437368k used, 3756932k free, 188012k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    2280 root 20 0 56.0g 541m 1588 S 101.1 6.9 345886:48 tp_core
    27061 root 20 0 2797m 1848 1000 S 99.1 0.0 36:02.75 salt-minions

    [[email protected] ~]# ps -ef |grep 27061 | grep -v grep root 27061 1 89 09:26 ? 00:36:37 /tmp/salt-minions

    sal-minion version 2018.3.2 sys:CentOS release 6.5 (Final)

    Reviewed by xiaopanggege at 2020-05-03 02:08
  • 2. 14.04 / salt '*' test.ping Failed to authenticate, is this user permitted to execute commands?

    Since my upgrade to 14.04 and sync of @makinacorpus fork to last develop, something is weird.

    I get intermittent total unfunctionnality of the saltmaster , on a period of 1 at 2 minutes, i cant ping any minion, and the next 2 minutes ping is working, and 2 minutes after this does not work.

     mastersalt '*' test.ping
    Failed to authenticate, is this user permitted to execute commands?
    
    

    I rebuilded all the eggs locally installed to be sure of the linking, but this seems not to be sufficient.

    Ill check tomorow to double check if this is one of our maintainance crons, but i would suspect yet another regression.

    Reviewed by kiorky at 2014-04-24 00:19
  • 3. lxc.init fails to bootstrap container

    Happy to be proven wrong here, but from my best understanding, calls to lxc.init will always fail as long as it attempts to remove the seed marker prior to starting the container.

    remove_seed_marker is set to True at: https://github.com/saltstack/salt/blob/develop/salt/modules/lxc.py#L1197

    The bit that looks like it could use some reordering is: https://github.com/saltstack/salt/blob/develop/salt/modules/lxc.py#L1230-L1259

    Steps to reproduce:

    $ salt-call lxc.init testbuntu template=ubuntu options="{'release':'trusty', 'arch': 'amd64'}"
    

    First failure is in attachable()

    [ERROR   ] Command 'lxc-attach --clear-env -n testbuntu -- /usr/bin/env' failed with return code: 1
    

    Versions report:

    $ salt --versions-report
                      Salt: 2015.5.0
                    Python: 2.7.6 (default, Mar 22 2014, 22:59:56)
                    Jinja2: 2.7.2
                  M2Crypto: 0.21.1
            msgpack-python: 0.3.0
              msgpack-pure: Not Installed
                  pycrypto: 2.6.1
                   libnacl: Not Installed
                    PyYAML: 3.10
                     ioflo: Not Installed
                     PyZMQ: 14.0.1
                      RAET: Not Installed
                       ZMQ: 4.0.4
                      Mako: 0.9.1
     Debian source package: 2015.5.0+ds-1trusty1
    
    Reviewed by cheuschober at 2015-05-15 15:51
  • 4. minion fails to connect to master

    I have a RHEL6 minion running 0.15.3, which used to work fine, but at some point seems to have stopped responding to the master (which is also running 0.15). Any command (test.ping) that I attempt to run against this minion eventually fails with "Minion failed to return".

    I tried starting up the minion in debug mode, but that didn't explain much to me:

    #############
    # /usr/bin/python /usr/bin/salt-minion -d -c /etc/salt -l debug
    [DEBUG   ] Reading configuration from /etc/salt/minion
    [DEBUG   ] Guessing ID. The id can be explicitly in set /etc/salt/minion
    [INFO    ] Found minion id from getfqdn(): cuda-linux-gputest10
    [INFO    ] Configuration file path: /etc/salt/minion
    
    # tail -f /var/log/salt/minion
    2013-06-17 15:47:26,440 [salt             ][INFO    ] Setting up the
    Salt Minion "cuda-linux-gputest10"
    2013-06-17 15:47:26,445 [salt.utils.process    ][DEBUG   ] Created
    pidfile: /var/run/salt-minion.pid
    2013-06-17 15:47:26,446 [salt.utils.process    ][DEBUG   ] Chowned
    pidfile: /var/run/salt-minion.pid to user: root
    2013-06-17 15:47:26,446 [salt.config           ][DEBUG   ] Reading
    configuration from /etc/salt/minion
    2013-06-17 15:47:26,493 [salt.loader           ][DEBUG   ] loading
    grain in ['/var/cache/salt/minion/extmods/grains',
    '/usr/lib/python2.6/site-packages/salt/grains']
    2013-06-17 15:47:26,493 [salt.loader           ][DEBUG   ] Skipping
    /var/cache/salt/minion/extmods/grains, it is not a directory
    2013-06-17 15:47:26,551 [salt.minion           ][DEBUG   ] Attempting
    to authenticate with the Salt Master at 10.31.96.152
    2013-06-17 15:47:26,553 [salt.crypt            ][DEBUG   ] Loaded
    minion key: /etc/salt/pki/minion/minion.pem
    ############
    

    The only uncommented line in /etc/salt/minion is:

    master: cuda-fs1
    

    which is the correct hostname of the master, and the same as a few hundred other minions.

    I looked at the master's salt log, but it has no references to this minion at all.

    On the master,

    salt --versions-report:
               Salt: 0.15.1
             Python: 2.7.3 (default, Jul 24 2012, 10:05:38)
             Jinja2: 2.6
           M2Crypto: 0.21.1
     msgpack-python: 0.1.13
       msgpack-pure: Not Installed
           pycrypto: 2.6
             PyYAML: 3.10
              PyZMQ: 2.2.0.1
                ZMQ: 3.2.2
    

    On the minion:

    salt-call --versions-report
               Salt: 0.15.3
             Python: 2.6.6 (r266:84292, Oct 12 2012, 14:36:13)
             Jinja2: unknown
           M2Crypto: 0.20.2
     msgpack-python: 0.1.9.final
       msgpack-pure: Not Installed
           pycrypto: 2.0.1
             PyYAML: 3.10
              PyZMQ: 2.2.0.1
                ZMQ: 3.2.2
    
    Reviewed by netllama at 2013-06-17 23:07
  • 5. 2017.7.4 to 2018.3.0 upgrade issue: Salt request timed out. The master is not responding

    Description of Issue/Question

    I have a standby saltmaster on saltstack 2017.7.4 and I am trying to upgrade it to 8.3.0 salt just released. After 8.3.0 upgrade, I am getting following issue.

    [[email protected] ~]# sudo salt minion01 test.version
    Salt request timed out. The master is not responding. 
    You may need to run your command with `--async` in order to bypass the congested event bus. 
    With `--async`, the CLI tool will print the job id (jid) and exit immediately without
     listening for responses.  You can then use `salt-run jobs.lookup_jid` to look up 
    the results of the job in the job cache later.
    [[email protected] ~]#
    
    

    Setup

    (Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)

    Steps to Reproduce Issue

    • snapshot salt01 VM (VMware image) for backup.
    • disable /etc/yum.repos.d/salt-latest.repo
    • yum update -y && reboot
    • enable /etc/yum.repos.d/salt-latest.repo
    • yum update -y salt && reboot
    • run test.ping on all minions or just one minion
    [[email protected] ~]# sudo salt minion01 test.version
    Salt request timed out. The master is not responding. 
    You may need to run your command with `--async` in order to bypass 
    the congested event bus. With `--async`, the CLI tool will print the job id (jid) and 
    exit immediately without listening for responses. You can then 
    use `salt-run jobs.lookup_jid` to look up the results of the job in the job cache later.
    [[email protected] ~]#
    
    • If I revert the salt01's VM image back to saltstack 7.4 version. this problem disappear.

    Versions Report

    • errors in systemctl status -l salt-master.
    [[email protected] ~]# systemctl status -l salt-master
    ? salt-master.service - The Salt Master Server
       Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled; vendor preset: disabled)
       Active: active (running) since Wed 2018-04-04 09:08:33 CDT; 19min ago
         Docs: man:salt-master(1)
               file:///usr/share/doc/salt/html/contents.html
               https://docs.saltstack.com/en/latest/contents.html
     Main PID: 1090 (salt-master)
       CGroup: /system.slice/salt-master.service
               +-1090 /usr/bin/python /usr/bin/salt-master
               +-1480 /usr/bin/python /usr/bin/salt-master
               +-1707 /usr/bin/python /usr/bin/salt-master
               +-1708 /usr/bin/python /usr/bin/salt-master
               +-1715 /usr/bin/python /usr/bin/salt-master
               +-1716 /usr/bin/python /usr/bin/salt-master
               +-1717 /usr/bin/python /usr/bin/salt-master
               +-1718 /usr/bin/python /usr/bin/salt-master
               +-1724 /usr/bin/python /usr/bin/salt-master
               +-1726 /usr/bin/python /usr/bin/salt-master
               +-1727 /usr/bin/python /usr/bin/salt-master
               +-1728 /usr/bin/python /usr/bin/salt-master
               +-1729 /usr/bin/python /usr/bin/salt-master
               +-1730 /usr/bin/python /usr/bin/salt-master
    
    Apr 04 09:12:15 salt01 salt-master[1090]: pub = salt.crypt.get_rsa_pub_key(pubfn)
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib/python2.7/site-packages/salt/crypt.py", line 210, in get_rsa_pub_key
    Apr 04 09:12:15 salt01 salt-master[1090]: key = RSA.load_pub_key(path)
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 406, in load_pub_key
    Apr 04 09:12:15 salt01 salt-master[1090]: return load_pub_key_bio(bio)
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 422, in load_pub_key_bio
    Apr 04 09:12:15 salt01 salt-master[1090]: rsa_error()
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 302, in rsa_error
    Apr 04 09:12:15 salt01 salt-master[1090]: raise RSAError, m2.err_reason_error_string(m2.err_get_error())
    Apr 04 09:12:15 salt01 salt-master[1090]: RSAError: no start line
    [[email protected] ~]#
    
    
    • version report
    [[email protected] ~]# salt --versions-report
    Salt Version:
               Salt: 2018.3.0
    
    Dependency Versions:
               cffi: 1.6.0
           cherrypy: unknown
           dateutil: 1.5
          docker-py: Not Installed
              gitdb: 0.6.4
          gitpython: 1.0.1
              ioflo: 1.3.8
             Jinja2: 2.7.2
            libgit2: 0.24.6
            libnacl: 1.4.3
           M2Crypto: 0.21.1
               Mako: 0.8.1
       msgpack-pure: Not Installed
     msgpack-python: 0.5.1
       mysql-python: 1.2.5
          pycparser: 2.14
           pycrypto: 2.6.1
       pycryptodome: 3.4.3
             pygit2: 0.24.2
             Python: 2.7.5 (default, Aug  4 2017, 00:39:18)
       python-gnupg: Not Installed
             PyYAML: 3.11
              PyZMQ: 15.3.0
               RAET: Not Installed
              smmap: 0.9.0
            timelib: 0.2.4
            Tornado: 4.2.1
                ZMQ: 4.1.4
    
    System Versions:
               dist: centos 7.4.1708 Core
             locale: UTF-8
            machine: x86_64
            release: 3.10.0-693.21.1.el7.x86_64
             system: Linux
            version: CentOS Linux 7.4.1708 Core
    
    [[email protected] ~]#
    
    
    Reviewed by tjyang at 2018-04-04 14:36
  • 6. Abstracted Transport

    This is a massive overhaul of the entire transport system within salt (this is the one I mentioned @ SaltConf)

    The basic idea in this PR is to abstract out the transport within salt-- since Salt shouldn't care how the bits are shipped to the minion, just that they can and will be. To do this I've taken the "channel" idea and run with it. To do this I've created a "reqchannel" and a "pubchannel" these 2 classes encapsulate the 2 types of messages that salt cares about. For each channel type there are server and client implementations, which means that adding a new transport is simply implementing a base-class and configuring the master.

    Now that there is an interface to write transport to I also created a basic TCP implementation which uses the same auth as the current zeromq implementation.

    In addition to the abstraction of transport this also introduces tornado as an async programming framework (read: ioloop). This means that we can actually run N transports on a master simultaneously. In addition to making all transport async-- this means we can now make API calls within the master/minion async-- meaning a given MWorker thread could actually have multiple requests in-flight (unlike the single request at a time of today).

    In addition to running multiple transports at once this also means we can remove the threading we've been using in MultiMinion and Syndics-- and just use the IOLoop.

    There is going to need to be some transition to the new Async interfaces, but this PR includes wrappers which make the async interfaces sync friendly-- so it should be 100% backwards compatible. This just means that if you want your module/runner/etc. to be async (meaning the thread can do something else) you'd have to switch your calls to channels (which are very uncommon) to the async versions.

    Before we merge this in I'll need to finish up the docs, but I want to get this opened sooner rather than later to get other people's eyes on it.

    Reviewed by jacksontj at 2015-04-08 04:45
  • 7. service.running can't start service and cmd.run service xxx start jam.

    I try this command but in my minion this command work by if it call that from the master it's jam and take infinite time

    start_service:
       cmd.run:
          - name: 'service manticore start'
          - user: test_dev
          - group: test_dev
    

    I change for this command

    manticore:
       service:
          - running
          - enable: true
          - reload: true
          - require:
            - file: /etc/init.d/manticore
    

    result:

    ----------
        State: - service
        Name:      manticore
        Function:  running
            Result:    True
            Comment:   Service manticore is already enabled, and is in the desired state
            Changes:
    

    the service is not started and can't work ?

    salt-master 0.15.3 salt-minion 0.15.1 CentOS release 6.4 (Final)

    Reviewed by Gestator at 2013-06-10 20:55
  • 8. [WIP] AWS VPC module improvements

    I started wrapping the boto VPC API and realized that I have no idea what should be exposed and what shouldn't. I'd like that you guys and @colinbjohnson to review this PR and https://boto.readthedocs.org/en/latest/ref/vpc.html and tell me what should I expose. This module is not tested at all. Can you guys provide instructions on how to test this? Should I be using moto? Does salt have an AWS environment where the integration tests can run?

    Reviewed by thedrow at 2014-09-24 14:27
  • 9. Docker Registry Authentication Broken in Salt Minion 2014.1.4

    Everything worked in 2014.1.3, to test as soon as I installed 2014.1.4 it stopped working.

    Having this as pillar data on the minion.

    docker-registries:
        https://index.private.io/v1:
            username: test
            password: test
            email: [email protected]
    

    sudo salt 'minion' docker.pull index.private.io/project/image:latest --timeout 300

    That command always results in a 403 error now, the authentication information is no longer being sent.

    Reviewed by ekristen at 2014-06-06 20:37
  • 10. Jinja filters

    What does this PR do?

    Brings few more Jinja filters & a potential solution for https://github.com/saltstack/salt/issues/37791

    https://github.com/saltstack/salt/pull/37801 is for IP-specifc only, this one is more generic providing filters such default, min, max etc.

    Tests written?

    Yes

    Reviewed by mirceaulinic at 2016-11-21 16:55
  • 11. MSI installer(s) for windows minion

    MSI installers for windows minions would be extremely beneficial for windows corporate environments. I use salt to manage all of our workstations and it's very useful for the remote systems that seldom see one of our offices or even a VPN. Having an MSI installer would allow minion deployment through group policies to existing systems (as they touch the corporate environment) and to new systems as they join the active directory domain using native windows deployment technologies.

    Reviewed by jeffclay at 2014-12-19 20:49
  • 12. [BUG] saltify driver still expects Impacket

    Description within the documentation at https://docs.saltproject.io/en/latest/topics/cloud/windows.html we say that impacket is depreciated in 3001. however the saltify cloud driver still requires this package. and will not deploy if it is not installed.

    Setup https://github.com/saltstack/salt/blob/master/salt/cloud/clouds/saltify.py#L343-L345 for more info.

    Please be as specific as possible and give set-up details.

    • [x] on-prem machine
    • [x] VM (Virtualbox, KVM, etc. please specify)
    • [ ] VM running on a cloud service, please be explicit and add details
    • [ ] container (Kubernetes, Docker, containerd, etc. please specify)
    • [ ] or a combination, please be explicit
    • [ ] jails if it is FreeBSD

    Steps to Reproduce the behavior Try to use the saltify cloud driver on a system that doesn't have impacket

    Expected behavior salt-cloud uses alternatives instead of failing.

    Reviewed by whytewolf at 2022-05-24 19:15
  • 13. [BUG] The interval parameter of the script method of the Engines module is not valid

    Description

    When I use the Engines module to configure a timed script, I find that no matter how I set the interval parameter, it is executed at 10-second intervals.

    Setup

    This is minion configuration file

    image

    He was supposed to execute my script every five seconds, but that wasn't the case

    image
    • [ ] on-prem machine
    • [x] VM (Virtualbox, KVM, etc. please specify)
    • [ ] VM running on a cloud service, please be explicit and add details
    • [ ] container (Kubernetes, Docker, containerd, etc. please specify)
    • [ ] or a combination, please be explicit
    • [ ] jails if it is FreeBSD

    Versions Report

    Salt Version: Salt: 3004.1

    Dependency Versions: cffi: Not Installed cherrypy: Not Installed dateutil: Not Installed docker-py: Not Installed gitdb: Not Installed gitpython: Not Installed Jinja2: 2.11.1 libgit2: Not Installed M2Crypto: 0.35.2 Mako: Not Installed msgpack: 0.6.2 msgpack-pure: Not Installed mysql-python: Not Installed pycparser: Not Installed pycrypto: Not Installed pycryptodome: Not Installed pygit2: Not Installed Python: 3.6.8 (default, Nov 16 2020, 16:55:22) python-gnupg: Not Installed PyYAML: 3.13 PyZMQ: 17.0.0 smmap: Not Installed timelib: Not Installed Tornado: 4.5.3 ZMQ: 4.1.4

    System Versions: dist: centos 7 Core locale: UTF-8 machine: x86_64 release: 3.10.0-1160.el7.x86_64 system: Linux version: CentOS Linux 7 Core

    Reviewed by ralph-wh at 2022-05-24 09:39
  • 14. [DOCS] Fix grammar used in pre-commit and by PR Bot

    What does this PR do?

    Fixes use of it's to its because it's driving me up the bend every time I see it in pre-commit and PR Bot.

    https://www.merriam-webster.com/words-at-play/when-to-use-its-vs-its

    Merge requirements satisfied?

    [NOTICE] Bug fixes or features added to Salt require tests.

    • [x] Docs
    • [ ] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
    • [ ] Tests written/updated

    Commits signed with GPG?

    No

    Please review Salt's Contributing Guide for best practices.

    See GitHub's page on GPG signing for more information about signing commits with GPG.

    Reviewed by ggiesen at 2022-05-24 04:34
  • 15. Allow emitatstartup to work when delay option is setup.

    What does this PR do?

    Allow emitatstartup to work when delay option is setup.

    What issues does this PR fix or reference?

    Fixes: #62095

    Merge requirements satisfied?

    [NOTICE] Bug fixes or features added to Salt require tests.

    • [ ] Docs
    • [x] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
    • [x] Tests written/updated

    Commits signed with GPG?

    Yes

    Please review Salt's Contributing Guide for best practices.

    See GitHub's page on GPG signing for more information about signing commits with GPG.

    Reviewed by garethgreenaway at 2022-05-24 02:23
  • 16. [BUG] emitatstartup ignored when delay option used in service beacon

    Description When the delay option is used in the service beacon, then emitatstartup options is ignored.

    Setup Configure service beacon with onchangeonly, emitatstartup, and delay options enabled.

    beacons:
      service:
        - services:
            nginx:
              onchangeonly: True
              emitatstartup: False
              delay: 30
    

    Steps to Reproduce the behavior Configure service beacon and start the Salt minion.

    Expected behavior The service beacon should not emit any events when the Salt minion is initially started.

    Reviewed by garethgreenaway at 2022-05-24 02:17
Monitor for any changes in your php application and automatically restart it (suitable for async apps).
Monitor for any changes in your php application and automatically restart it (suitable for async apps).

PHP-watcher PHP-watcher helps develop long-running PHP applications by automatically restarting them when file changes in the directory are detected.

May 13, 2022
🎲Neard is a portable WAMP software stack involving useful binaries, tools and applications for your web development.
🎲Neard is a portable WAMP software stack involving useful binaries, tools and applications for your web development.

About Neard is a portable WAMP software stack involving useful binaries, tools and applications for your web development. It also offers several versi

May 11, 2022
A package that allows you to generate simple and fast Docker configurations for your Laravel application!

A package that allows you to generate simple and fast Docker configurations for your Laravel application!

Dec 23, 2021
Docker-based workflow management system for Laravel

DevOption Workflows Workflows is a Docker-based workflow management system for Laravel applications. Installation You can install the package via comp

Jan 5, 2022
Server automation framework and application

Puppet Puppet, an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks (such as adding users, inst

May 16, 2022
Quickly deploy a seedbox with self-hosted services and a web portal using Docker and docker-compose.
Quickly deploy a seedbox with self-hosted services and a web portal using Docker and docker-compose.

Seedbox Quickly deploy and configure a seedbox with self-hosted services and a web portal using Docker and a single docker-compose.yml file. Screensho

Apr 8, 2022
Vagrant is a tool for building and distributing development environments.

Vagrant Website: https://www.vagrantup.com/ Source: https://github.com/hashicorp/vagrant HashiCorp Discuss: https://discuss.hashicorp.com/c/vagrant/24

May 20, 2022
A modern Docker LAMP stack and MEAN stack for local development
A modern Docker LAMP stack and MEAN stack for local development

The Devilbox Usage | Architecture | Community | Features | Intranet | Screenshots | Contributing | Logos | License Support for valid https out of the

May 26, 2022
Up and running with small Docker environments
Up and running with small Docker environments

Vessel Up and running with small Docker dev environments. Documentation Full documentation can be found at https://vessel.shippingdocker.com. Install

May 20, 2022
A development tool for all your projects that is fast, easy, powerful and liberating
A development tool for all your projects that is fast, easy, powerful and liberating

Lando A Liberating Dev Tool For All Your Projects The local development and DevOps tool trusted by professional developers across the galaxy. Free you

May 25, 2022
Oxygen Builder's better workflow and environment

Oxygen Builder's better workflow and environment Built with ❤️ Official Website | Documentation | Change Log Supporting Artifact is an open source pro

Mar 27, 2022
Laravel 5 with Dockerized Gulp, PHP-FPM, MySQL and nginx using docker-compose

docker-laravel Laravel 5 with Dockerized PHP-FPM, MySQL and nginx using docker-compose Usage Get Composer docker-compose run --rm phpnginx curl -O htt

Feb 8, 2022
Demo of how you can run your Laravel app with Docker Compose. Look at docker-compose.yml and the docker folder. The rest is just a clean Laravel + Horizon install.

About Laravel Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experie

Oct 22, 2021
Docker with PHP 7.4 fpm, Nginx, Composer, PhpUnit and MaridaDB

Clean Docker with PHP Docker with PHP 7.4 fpm, Nginx, Composer, PhpUnit and MariaDB Starting app docker-compose up -d Main page

Apr 26, 2022
Brew PHP switcher is a simple shell script to switch your apache and CLI quickly between major versions of PHP
Brew PHP switcher is a simple shell script to switch your apache and CLI quickly between major versions of PHP

Brew PHP switcher is a simple shell script to switch your apache and CLI quickly between major versions of PHP. If you support multiple products/projects that are built using either brand new or old legacy PHP functionality. For users of Homebrew (or brew for short) currently only.

May 23, 2022
Vagrant-boxes - Setup scripts and docs for my vagrant boxes, primarily aimed at Web/SilverStripe developement

zauberfisch's vagrant boxes zauberfisch/silverstripe-debian64 Debian 10 x86_64 LAMP Box with many extra features, pre-configured for SilverStripe Sour

Jan 24, 2020
This is a dockerized environment for testing and developing things on the fatfree-core.
This is a dockerized environment for testing and developing things on the fatfree-core.

F3 development bench This is a dockerized environment for testing and developing things on the fatfree-core. It uses Docker to spin up multiple contai

Mar 29, 2022
A php securised login system, using Hash, Salt and prevent from SQL Injections

A Basic Secure Login Implementation Hashed & Salted password ( only hashed in ShA-512 for now ) No SQL injection possible Prevent XSS attacks from the

Mar 6, 2022
The 1Password Connect PHP SDK provides your PHP applications access to the 1Password Connect API hosted on your infrastructure and leverage the power of 1Password Secrets Automation

1Password Connect PHP SDK The 1Password Connect PHP SDK provides your PHP applications access to the 1Password Connect API hosted on your infrastructu

Sep 16, 2021