Go to file
2022-12-16 20:07:28 -05:00
.cargo wasm fixes 2022-11-29 22:51:51 -05:00
.vscode fix cooperative cancellation 2022-06-15 14:05:04 -04:00
doc refactor 2022-11-26 21:37:23 -05:00
docs/guide Adds markdown version of guide 2022-10-18 12:14:14 -07:00
external checkpoint 2022-12-16 20:07:28 -05:00
files Add Test CA and simple certs for testing 2021-11-22 09:02:41 -05:00
package receipt rework and discovery rework 2022-05-28 10:07:57 -04:00
scripts flutter work 2022-12-03 12:36:06 -05:00
veilid-cli route grooming fix 2022-12-15 18:41:44 -05:00
veilid-core checkpoint 2022-12-16 20:07:28 -05:00
veilid-flutter checkpoint 2022-12-16 20:07:28 -05:00
veilid-server windows support and more recursion fixes 2022-12-01 19:08:40 -05:00
veilid-tools bug fixes 2022-12-15 20:52:24 -05:00
veilid-wasm checkpoint 2022-12-16 20:07:28 -05:00
.earthlyignore add eartly build 2022-01-09 15:17:36 -05:00
.gitignore WIP, further docs 2022-09-19 19:18:46 -06:00
.gitlab-ci.yml Add submodule strategyt to build 2022-11-26 22:18:08 -07:00
.gitmodules refactor 2022-11-26 21:37:23 -05:00
Cargo.lock test work 2022-12-01 14:32:02 -05:00
Cargo.toml build updates 2022-11-30 16:15:54 -05:00
Earthfile remove cruft 2022-12-01 18:25:53 -05:00
README.md Correct README link 2022-09-19 20:23:13 -06:00
setup_linux.sh updates 2022-11-02 20:42:07 -04:00
setup_macos.sh flutter work 2022-12-03 18:08:53 -05:00
setup_windows.bat windows support and more recursion fixes 2022-12-01 19:08:40 -05:00

Veilid

Introduction

Obtaining the source code

git clone --recurse-submodules git@gitlab.hackers.town:veilid/veilid.git

Dependencies

GNU/Linux

Development of Veilid on GNU/Linux requires a Debian variant such as Debian itself, Ubuntu or Mint. Pull requests to support other distributions would be welcome!

Running the setup script requires:

  • Android SDK and NDK
  • Rust

You may decide to use Android Studio here to maintain your Android dependencies. If so, use the dependency manager within your IDE. If you plan on using Flutter for Veilid development, the Android Studio method is highly recommended as you may run into path problems with the 'flutter' command line without it. If you do so, you may skip to [Run Veilid setup script](#Run Veilid setup script).

  • build-tools;30.0.3
  • ndk;22.0.7026061
  • cmake;3.22.1

Setup Dependencies using the CLI

Otherwise, you may choose to use Android sdkmanager. Follow the installation instructions for sdkmanager here, then use the command line to install the requisite package versions:

sdkmanager --install "build-tools;30.0.3"
sdkmanager --install "ndk;22.0.7026061"
sdkmanager --install "cmake;3.22.1"

Export environment variables and add the Android SDK platform-tools directory to your path.

cat << EOF >> ~/.profile 
export ANDROID_SDK_ROOT=<path to sdk>
export ANDROID_NDK_HOME=$ANDROID_SDK_ROOT/ndk/22.0.7026061
export PATH=\$PATH:$ANDROID_SDK_ROOT/platform-tools
EOF

Run Veilid setup script

Now you may run the Linux setup script to check your development environment and pull the remaining Rust dependencies:

./setup_linux.sh

Run the veilid-flutter setup script (optional)

If you are developing Flutter applications or the flutter-veilid portion, you should install Android Studio, and run the flutter setup script:

cd veilid-flutter
./setup_flutter.sh

macOS

Development of Veilid on MacOS is possible on both Intel and ARM hardware.

Development requires:

  • Android Studio
  • Xcode, preferably latest version
  • Homebrew here
  • Android SDK and NDK
  • Rust

You will need to use Android Studio here to maintain your Android dependencies. Use the SDK Manager in the IDE to install the following packages (use package details view to select version):

  • Android SDK Build Tools (30.0.3)
  • NDK (Side-by-side) (22.0.7026061)
  • Cmake (3.22.1)
  • Android SDK Command Line Tools (latest) (7.0/latest)

Setup command line environment

Export environment variables and add the Android SDK platform-tools directory to your path.

cat << EOF >> ~/.zshenv
export ANDROID_SDK_ROOT=$HOME/Library/Android/sdk
export ANDROID_NDK_HOME=$HOME/Library/Android/sdk/ndk/22.0.7026061
export PATH=\$PATH:$HOME/Library/Android/sdk/platform-tools
EOF

Run Veilid setup script

Now you may run the MacOS setup script to check your development environment and pull the remaining Rust dependencies:

./setup_macos.sh

Run the veilid-flutter setup script (optional)

If you are developing Flutter applications or the flutter-veilid portion, you should install Android Studio, and run the flutter setup script:

cd veilid-flutter
./setup_flutter.sh

Windows

TODO

Running the Application(s)

Veilid Server

In order to run the veilid-server locally:

cd ./veilid-server
cargo run

In order to see what options are available:

cargo run -- --help

Configuration

veilid-server has a wealth of configuration options. Further documentation on the format of the veilid-server.conf file may be found in the project /doc directory.

When running veilid-server in a Unix-like environment, the application will look for its config file under /etc/veilid-server/. If the config file is not found in this location, veilid-server will follow the XDG user directory spec and look in ~/.config/veilid-server.

When running under Windows, the veilid-server.conf file may be created at C:\Users\<user>\AppData\Roaming\Veilid\Veilid\, and when running under macOS, at /Users/<user>/Library/Application Support/org.Veilid.Veilid.

Veilid CLI

In order to connect to your local veilid-server:

cd ./veilid-cli
cargo run

Similar to veilid-server, you may see CLI options by typing:

cargo run -- --help

Building the Application

Linux Packages

Veilid server and cli can be built locally using the Earthly framework. After installing earthly on your local machine, you may use the earthly cli to initiate a build:

earthly +package-linux

This will assemble all dependencies and build .deb packages for both amd64 and arm64 platforms. Earthly, built on Docker, caches build layers, so after a longer first build, subsequent builds should be much quicker.

During development, you may want to kick off specific build steps. To see a list of the build steps configured, consult the Earthfile, or you may use the earthly cli:

earthly ls