docs/getting-started/install.md
To install PhoneInfoga, you'll need to download the binary or build the software from its source code.
!!! info For now, only Linux, MacOS and Windows are supported. If you don't see your OS/arch on the release page on GitHub, it means it's not explicitly supported. You can build from source by yourself anyway. Want your OS to be supported ? Please open an issue on GitHub.
Follow the instructions :
You can also do it from the terminal (UNIX systems only) :
# Add --help at the end of the command for a list of install options
bash <( curl -sSL https://raw.githubusercontent.com/sundowndev/phoneinfoga/master/support/scripts/install )
sudo install ./phoneinfoga /usr/local/bin/phoneinfoga
./phoneinfoga version
To ensure your system is supported, please check the output of echo "$(uname -s)_$(uname -m)" in your terminal and see if it's available on the GitHub release page.
PhoneInfoga is now available on Homebrew. Homebrew is a free and open-source package management system for Mac OS X. Install the official phoneinfoga formula from the terminal.
brew install phoneinfoga
!!! info
If you want to use the beta channel, you can use the next tag, it's updated directly from the master branch. But in most cases we recommend using latest, v2 or stable tags to only get release updates.
You can pull the repository directly from Docker hub
docker pull sundowndev/phoneinfoga:latest
Then run the tool
docker run --rm -it sundowndev/phoneinfoga version
You can use a single docker-compose file to run the tool without downloading the source code.
version: '3.7'
services:
phoneinfoga:
container_name: phoneinfoga
restart: on-failure
image: sundowndev/phoneinfoga:latest
command:
- "serve"
ports:
- "80:5000"
You can download the source code, then build the docker images
Build the image
docker-compose build
docker-compose run --rm phoneinfoga --help
docker-compose up -d
Edit docker-compose.yml and add the --no-client option
# docker-compose.yml
command:
- "serve"
- "--no-client"
All the output is sent to stdout, so it can be inspected by running:
docker logs -f <container-id|container-name>