If you wish to delete the Docker volume containing the Trillian Log database, you may docker volume delete trillian-data. Alternatively, you may docker-compose down and, if you wish docker-compose rm from within the directory where you created the docker-compose.yml file. You may terminate the Docker Compose services by CTRL-C’ing the process. The client puts-gets and then terminates. Then: drop database if exists test create database test create user if not exists identified by 'zaphod' grant all on test.* to docker run \ -interactive -tty \ -net=host \ -volume=$Īnd you should see: Establishing connection w/ Trillian Log Server Creating new Trillian Log Client Creating Server using LogID Creating Creating a 'Thing' and something 'Extra' Creating: Thing Creating Submitting it for inclusion in the Trillian Log Entered Marshaling: Thing Entered ok ok Retrieving it from the Trillian Log Entered Marshaling: Thing hash: 02a1829d. NB Trillian is named after a character in the Hitchhikers’ Guide to the Galaxy.
#Trillian web client password
Run your preferred MySQL database: docker run \ -name=database \ -env=MYSQL_ALLOW_EMPTY_PASSWORD=yes \ -mount=source= trillian-data,target=/var/lib/mysql \ -publish=3306:3306 mariadb:10.4įrom a second shell, connect to the database engine, create a database test with a user test with a password zaphod. Let’s create a Docker Volume to persist the database: docker volume create trillian-data Our Trillian sample application aka “personality”.A Trillian Log Server with which we interact.A database (MySQL|MariaDB) to persist the logs.If - like me - your head explodes, read on… If that content is the level you need to get started, I recommend you stop reading this and continue there.
The Trillian team provides documentation starting with the README on the repo. Perhaps rounding out the sample a Rust client let’s see….In the next post, we’ll build a basic gRPC client-server personality.In this post, we’ll get booted into Trillian and append data to a log.As a prospective customer of the team, I’d expect you’d receive even better attention than me -) Outline I’ve tried to keep the majority of my communications with the Trillian team in the open: on the team’s public Google Group and using GitHub issues. I’m endeavoring to fill the role of an external developer to help the Trillian team understand this experience and improve its documentation, samples etc.
Solicit feedback from the Trillian team to improve my understandingįull-dislosure: I’m a Googler but not part of the Trillian team.Clarify my understanding through an explanation.
#Trillian web client how to
Engineers are excellent at building wonderful technologies but often deficient when it comes to explaining to us mortals how to use them! In a short series of posts, I’m going to document my experience in prototyping an Trillian application (Trillianeers call these “personalities”) for three reasons: It is an open-source project and is the foundation of Certificate Transparency, Key Transparency, the Go team’s Go Module Mirror ( proposal) and a few not-yet-public applications. Google Trillian provides a tamper-proof append-only log (and upcoming log-backed map).
0 kommentar(er)
