8.9 KiB
FakeYou Development Setup (bare metal)
This document describes how to run the FakeYou infrastructure on your development machine's bare metal (no containers).
Setup instructions and development were tested and known to work on the following platforms:
- Mac OS (Apple M2 silicon)
- Ubuntu 22.04
- Windows Subsystem for Linux (Ubuntu 22.04 distro) aka "WSL"
The applications (binary targets) you might be interested in running include, but are not limited to:
storyteller-web, the HTTP API serverdownload-job, which downloads models from the web and stores them in GCSinference-job, which downloads models from GCS and runs inference with them
Setup Instructions
(1) Install Rust
Install Rust using this guide. If it asks, you'll want "stable" Rust, not "nightly" Rust. If it doesn't ask, it defaults to "stable".
For Windows Subsystem for Linux, you'll want the WSL version, not the .exe file!
(2) Install the necessary libraries
Mac: (Lost the library list, but it should match Linux. Install Homebrew.)
Ubuntu 22.04 and WSL:
# If you haven't run apt before, you'll need to fetch the package list:
sudo apt update
# Install the dependencies
sudo apt install jq \
libmysqlclient-dev \
libsqlite3-dev \
pkgconf
(Note: jq is for combining mysql codegen outputs; pkgconf is if using openssl instead of rustls.)
(3) Install MySQL server
Mac:
brew install mysql
If mysql -uroot fails, reboot the machine:
sudo reboot now
Ubuntu 22.04 and WSL:
sudo apt install mysql-server
You may need to start MySQL (typically WSL),
sudo service mysql start
You may also have to change some socket file permissions (again, typically WSL):
sudo chmod g+rx /var/run/mysqld
sudo usermod -aG mysql $USER
newgrp mysql
(4) Install a storyteller user and table in MySQL
Connect to mysql:
# If the following command asks for a password, the password is typically "root"
sudo mysql -u root -p
Once in MySQL, run the following:
use mysql;
CREATE DATABASE storyteller;
CREATE USER 'storyteller'@'localhost' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON storyteller.* TO 'storyteller'@'localhost';
Then verify access with ./dev_mysql_connect.sh
(5) Install Diesel CLI (for MySQL migrations):
cargo install diesel_cli \
--no-default-features \
--features mysql,sqlite
As of this writing, Mac has some issues with Diesel CLI and requires a few extra dependencies to be installed:
brew install libpq
(6) Run the pending database migrations:
diesel migration run
You might get a scary message about "Encountered unknown type for Mysql: enum" -- you can ignore this
error (see below).
(7) (optional) Install the SQLx CLI (if doing database development)
# NB(bt,2023-10-04): "--no-default-features" not working
# cargo install sqlx-cli --no-default-features --features rustls,mysql,sqlite
cargo install sqlx-cli --features rustls,mysql,sqlite
We'll be using diesel to manage the migrations, but sqlx within the app to actually perform queries. Diesel is an immature ORM, which isn't a good tech bet, so we use sqlx as at-compile-time typesafe SQL.
(8) Install hosts file:
(This is the same for Linux, Mac, and WSL.)
If you're developing against the frontend, it'll target development domains (eg. dev.fakeyou.com) instead
of 127.0.0.1 or localhost. You can make your machine route domains to localhost by editing your hosts
file (located at /etc/hosts) to include the following configuration lines:
# 1) Edit hosts file with your editor of choice
#
# - sudo vi /etc/hosts
# - sudo nano /etc/hosts
#
# 2) Then paste:
#
127.0.0.1 dev.fakeyou.com
127.0.0.1 api.dev.fakeyou.com
127.0.0.1 devproxy.fakeyou.com
127.0.0.1 dev.storyteller.ai
127.0.0.1 api.dev.storyteller.ai
127.0.0.1 devproxy.storyteller.ai
(9) Install Redis
Mac: (TODO)
Ubuntu 22.04 and WSL:
sudo apt install redis
The server might need to be started on WSL,
sudo service redis-server start
(10) Install Elasticsearch (optional)
Mac: (TODO - haven't installed yet)
WSL: (TODO - haven't installed yet)
Ubuntu 22.04:
Install:
curl -fsSL https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo gpg --dearmor -o /usr/share/keyrings/elastic.gpg
echo "deb [signed-by=/usr/share/keyrings/elastic.gpg] https://artifacts.elastic.co/packages/7.x/apt stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-7.x.list
sudo apt update
sudo apt install elasticsearch
Configure:
# Edit /etc/elasticsearch/elasticsearch.yml
# Set the following:
network.host: localhost
Run:
sudo systemctl start elasticsearch
sudo systemctl enable elasticsearch
Verify:
curl -X GET 'http://localhost:9200'
Install Kibana (prototyping UI):
# Install
sudo apt-get install kibana
# Run
sudo /bin/systemctl daemon-reload
sudo /bin/systemctl enable kibana.service
sudo systemctl start kibana.service
# Access the Kibana Status Page:
# http://localhost:5601/status
# Access the query console UI:
# Click Sidebar > Management > Dev Tools > Console
# http://localhost:5601/
Extra reading:
(11) Run one or more applications:
To start the HTTP API server,
cargo run --bin storyteller-web
Note that this compiles and runs the "development" binary. It's faster and easier to debug than the
optimized "production" build. To build a fully optimized production release,
run cargo build --release --bin storyteller-web . Note that this will take much longer.
You may notice that this might not work right off the bat. You may need to specify some environment variables and supply some development secrets.
Secrets:
-
Global secrets (ask Brandon for these):
- Put
.env-secretsin the rootstoryteller-rustdirectory.
- Put
-
Per app secrets (ask Brandon for these):
- Put
storteller-web.development-secrets.envincrates/service/web/storyteller-web/config - Put
inference-job.development-secrets.envincrates/service/job/inference_job/config - Put
donwload-job.development-secrets.envincrates/service/job/download_job/config
- Put
DO NOT CHECK THESE SECRET FILES INTO THE REPO!
Environment config:
You may need to set local development paths for your environment. You can set these in .env-secrets too,
so that they won't be updated for other engineers.
# this should be the directory containing all of the "storyteller" projects:
STORYTELLER_ROOT = "/home/tensor/code/storyteller" # change this
# The following are entirely optional, but if you want to fine tune where each project lives, you may do so:
STORYTELLER_FRONTEND = "/somewhere/else/storyteller-frontend"
STORYTELLER_ML = "storyteller-ml"
STORYTELLER_RUST = "/Users/bt/Development/storyteller-rust"
To download some ML models, run:
cargo run --bin download-job
cargo run --bin tts-download-job
If you want to run both the HTTP API and the jobs, you'll need to run both processes in different terminals or tmux sessions.
Note also that the configurations pointing to the ML monorepo must be set up for each application. Additionally, some development secrets may be needed (ask the team to share).
To execute ML inference, run:
cargo run --bin inference-job
cargo run --bin tts-inference-job
Again, note that the configurations pointing to the ML monorepo must be set up for each application. Additionally, some development secrets may be needed (ask the team to share).
Solutions to Common Setup Problems
[Fix] Sqlx Error when Performing Schema Migrations
You might get this error message during migration,
Encountered unknown type for Mysql: enum
thread 'main' panicked at 'internal error: entered unreachable code: Mysql only supports a closed set of types.
If you ever see this error message please open an issue at https://github.com/diesel-rs/diesel
containing a dump of your schema definition.', diesel_cli/src/print_schema.rs:310:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
I haven't found the cause (it doesn't happen on newer installs), but the migrations appear to work regardless of this error message. You can essentially ignore it.
[Fix] Can't connect to local MySQL after install on Ubuntu
- If MySql in local dev can't be connected to, reset the accounts.