Unverified Commit 5a85b684 authored by Vasili Novikov's avatar Vasili Novikov
Browse files

Add nicer defaults

parent b6fdb6dc
Showing with 37 additions and 2 deletions
+37 -2
......@@ -8,7 +8,7 @@ authors = [
"Youp Mickers (copyright transferred to Polis) <polisyoup@gmail.com>",
]
edition = "2018"
publish = false # Since the project does not have a licence yet, prevent accidental publishing.
publish = false # Prevent accidental publishing
[dependencies]
......
......@@ -30,6 +30,11 @@ After this, you can run Pod with:
cargo run --release
```
Or with some development defaults:
```
./examples/run_development.sh
```
## Development
If you develop Pod, you might want to have faster build turn-around.
......
......@@ -15,7 +15,10 @@ services:
- /var/run/docker.sock:/var/run/docker.sock
environment:
- POD_IS_IN_DOCKER=true
# - POD_OWNER_HASHES=your-client's-key-hash
- POD_OWNER_HASHES=ANY
#- POD_ADDRESS=
#- POD_HTTPS_CERTIFICATE=
#- POD_USE_INSECURE_NON_TLS=
volumes:
db:
......
#!/bin/bash -euET
# You can use this to generate a self-signed certificate for Pod during development
if !test -e Cargo.toml; then
echo "Please run this script from Pod-s main directory."
exit 1
fi
if test -f data/pod.crt && test -f data/pod.key; then
echo "Skipping certificate generation as cert already exists"
exit 0
fi
exec openssl req -x509 -newkey rsa:4096 -keyout data/pod.key -out data/pod.crt -days 365 -nodes -subj "/C=US/ST=Oregon/L=Portland/O=Company Name/OU=Org/CN=www.example.com"
#!/bin/bash -euET
# This is an example of how you might run Pod during development.
# Do not ever attempt to ever use this script in production!
if !test -e Cargo.toml; then
echo "Please run this script from Pod-s main directory."
exit 1
fi
examples/generate_self-signed_certificate.sh
POD_OWNER_HASHES=ANY POD_HTTPS_CERTIFICATE=./data/pod RUST_LOG=pod=debug,info exec cargo run
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment