AppJail | Simple and easy-to-use tool for creating portable jails
kandi X-RAY | AppJail Summary
kandi X-RAY | AppJail Summary
AppJail is a Shell library. AppJail has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
AppJail is an open source framework entirely written in sh(1) and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Contribute your Makejail:
AppJail is an open source framework entirely written in sh(1) and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Contribute your Makejail:
Support
Quality
Security
License
Reuse
Support
AppJail has a low active ecosystem.
It has 40 star(s) with 0 fork(s). There are 2 watchers for this library.
It had no major release in the last 12 months.
There are 0 open issues and 3 have been closed. On average issues are closed in 0 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of AppJail is v2.5.1
Quality
AppJail has no bugs reported.
Security
AppJail has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
AppJail is licensed under the BSD-3-Clause License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
AppJail releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AppJail
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AppJail
AppJail Key Features
No Key Features are available at this moment for AppJail.
AppJail Examples and Code Snippets
No Code Snippets are available at this moment for AppJail.
Community Discussions
No Community Discussions are available at this moment for AppJail.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install AppJail
If you want to use a custom configuration file, create one in /usr/local/etc/appjail/appjail.conf. See more details in /usr/local/share/appjail/files/default.conf. Note: It is highly recommended to put the kernel modules suggested in this document in your loader.conf(5) file to correctly start the jails on boot.
To create a very basic jail, only two things are needed: obtaining the FreeBSD components (base.txz, lib32.txz, etc.) and creating the jail using those components. Using the appjail fetch command will download the MANIFEST file to check the components. Afterwards, AppJail will download the components. By default, AppJail will only download base.txz. AppJail will extract those components into its release directory. At this point, AppJail can create a jail using the appjail quick command. In the above example, appjail quick will create a jail named myjail. Using the start option, AppJail will start the jail after its creation. The login option simply logs into the jail after startup. The appjail fetch is not necessary to run again unless you need another release with different components. More complex examples will be shown later.
A Makejail file is a sequence of instructions, line by line, where each command and its arguments are separated by a single space (ascii: 0x20). As you can see in INCLUDE, a lot of useless information such as leading spaces, comments, empty lines and other similar things are discarded. When INCLUDE compiles all Makejails into a single Makejail, appjail makejail uses it to execute the instructions. The first stage to execute is build. This stage writes a script named buildscript that takes care of building the jail. When buildscript successfully completes its execution, the initscript is written to the jail directory, overwriting another initscript (if any). appjail makejail executes the commands in certain order. First, the ARG command is executed, second, OPTION (build only), and the rest ot the commands are executed in the order they appear. Now, we can write a Makejail. To run this Makejail, use appjail makejail. Remember that the -f parameter can use the methods described in INCLUDE and if you do not use a name for the jail with -j, a random name is chosen.
To create a very basic jail, only two things are needed: obtaining the FreeBSD components (base.txz, lib32.txz, etc.) and creating the jail using those components. Using the appjail fetch command will download the MANIFEST file to check the components. Afterwards, AppJail will download the components. By default, AppJail will only download base.txz. AppJail will extract those components into its release directory. At this point, AppJail can create a jail using the appjail quick command. In the above example, appjail quick will create a jail named myjail. Using the start option, AppJail will start the jail after its creation. The login option simply logs into the jail after startup. The appjail fetch is not necessary to run again unless you need another release with different components. More complex examples will be shown later.
A Makejail file is a sequence of instructions, line by line, where each command and its arguments are separated by a single space (ascii: 0x20). As you can see in INCLUDE, a lot of useless information such as leading spaces, comments, empty lines and other similar things are discarded. When INCLUDE compiles all Makejails into a single Makejail, appjail makejail uses it to execute the instructions. The first stage to execute is build. This stage writes a script named buildscript that takes care of building the jail. When buildscript successfully completes its execution, the initscript is written to the jail directory, overwriting another initscript (if any). appjail makejail executes the commands in certain order. First, the ARG command is executed, second, OPTION (build only), and the rest ot the commands are executed in the order they appear. Now, we can write a Makejail. To run this Makejail, use appjail makejail. Remember that the -f parameter can use the methods described in INCLUDE and if you do not use a name for the jail with -j, a random name is chosen.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page