You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-87Lines changed: 17 additions & 87 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,105 +44,35 @@ The idea is to use Arc as a single storage and manager for your passwords, encry
44
44
45
45
## Usage
46
46
47
-
You can find binary releases of Arc [here](https://github.com/evilsocket/arc/releases), if instead you want to build it from source, make sure you have Go >= 1.22.x installed and configured correctly, then clone this repository, install the dependencies and compile the `arc` server component:
47
+
The simplest way to run `arc` is as a Docker container. First, make sure to copy `sample_config.toml` into your own `config.toml`.
48
48
49
-
go install github.com/evilsocket/arc/cmd/arc@latest
50
-
51
-
Once you either extracted the release archive or compiled it yourself, copy `sample_config.toml` to a new `config.toml` file and customize it. The most important fields to change are the `secret` ( a key used for token authentication ), the `username` and the `password`, which is the `bcrypt` hash of the authentication password you want to use, you can generate a new one with:
52
-
53
-
arc password "your-new-password" <optional-cost>
49
+
The most important fields to change are the `secret` ( a key used for token authentication ), the `username` and the `password`, which is the `bcrypt` hash of the authentication password you want to use, you can generate a new one with:
54
50
55
-
Once everything is ready, youn can finally start the `arc` server:
56
-
57
-
arc -config config.toml -app arc
58
-
59
-
Now browse `https://localhost:8443/` ( or the address and port you configured ) and login with the configured credentials (make sure to add the generated HTTPS certificate as an exception in your browser).
51
+
```sh
52
+
docker run -it evilsocket/arc:latest password "your-new-password"<optional-cost>
53
+
```
60
54
61
55
**NOTE**
62
56
63
57
Other than the username and the password, during login you need to specify an additional encryption key. This second key is not used to login to the system itself but to encrypt and decrypt your records client side. You can specify different keys each time you login, as long as you remember which key you used to encrypt which record :)
64
58
65
-
## Configuration
59
+
Once everything is ready and you updated the configuration file, you can finally start the `arc` server:
66
60
67
-
This is the example configuration file you need to customize the first time.
# Validity in minutes of a JWT API token after it's being generated.
90
-
token_duration = 60
91
-
# If true, records bigger than 1024 bytes will be asynchronously gzipped and served as compressed streams to the client.
92
-
compression = true
93
-
94
-
# Tailscale specific configuration.
95
-
[tailscale]
96
-
# If true, will run this as a tailscale server node and won't be visible outside the tailscale network.
97
-
# In order to authenticate the node, set the TS_AUTHKEY environment variable or follow the onscreen instructions.
98
-
enabled = false
99
-
# Tailscale hostname, if left empty the system hostname will be used.
100
-
# NOTE: Make sure that HTTPS certificates are enabled for this tailscale host and that the hostname
101
-
# matches the certificate.
102
-
hostname = "stevie"
69
+
Now browse `https://localhost:8443/` ( or the address and port you configured ) and login with the configured credentials (make sure to add the generated HTTPS certificate as an exception in your browser).
103
70
104
-
# Periodic tasks.
105
-
[scheduler]
106
-
# Scheduler is enabled by default.
107
-
enabled = true
108
-
# Period in seconds of the scheduler.
109
-
period = 10
71
+
Alternatively, you can find binary releases of Arc [here](https://github.com/evilsocket/arc/releases).
# If reports are enabled, this SMTP configuration is required for email notifications.
119
-
[scheduler.reports.smtp]
120
-
address = "smtp.gmail.com"
121
-
port = 587
122
-
username = "youremail@gmail.com"
123
-
password = "your smtp password"
124
-
125
-
# Email notifications can be optionally encrypted with PGP.
126
-
[scheduler.reports.pgp]
127
-
enabled = true
128
-
129
-
# PGP Keys.
130
-
[scheduler.reports.pgp.keys]
131
-
# The ARC server PGP private key.
132
-
private = "~/server.private.key.asc"
133
-
# The emails recipient PGP public key.
134
-
public = "~/my.public.key.asc"
135
-
136
-
# Backup configuration.
137
-
[backups]
138
-
enabled = false
139
-
# Every 1800 run the command on that folder.
140
-
period = 1800
141
-
run = "scp arc-backup.tar user@backup-server:/media/arc_backup/"
142
-
folder = "/some/backup/path/"
143
-
```
73
+
If instead you want to build it from source, make sure you have Go >= 1.22.x installed and configured correctly, then clone this repository, install the dependencies and compile the `arc` server component:
144
74
145
-
It is necessary to change only the `secret`, `username` and `password` access parameters of Arc, while the others can be left to their default values.
75
+
go install github.com/evilsocket/arc/cmd/arc@latest
0 commit comments