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
Change links, remove duplicate content, clean up intro
* Change links to point to the page on this site, instead of the old page
* Theming and translating interviews already had pages on this site, merged with them instead
* Changed the overview to not point folks to the other site.
-[PDFtk](https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/) for
72
72
manipulating PDF files and templates
73
73
-[LetsEncrypt](https://letsencrypt.org/) for SSL certificate management
@@ -254,7 +254,7 @@ sudo shutdown -r now
254
254
for a security vulnerability.
255
255
- Beyond periodic updates, the version of Ubuntu software may need an upgrade. This is like going from
256
256
Windows 10 to 11, or macOS Ventura to Sonoma. Every 2 years, there's a new Ubuntu Long Term Support
257
-
(LTS) version. See [Rebuilding your AWS Lightsail instance](https://projects.suffolklitlab.org/legal-tech-class/docs/practical-guide-docassemble/rebuild-lightsail-instance).
257
+
(LTS) version. See [Rebuilding your AWS Lightsail instance](rebuild-lightsail-instance).
258
258
- What to back up - Keep a copy of the latest env.list file in case a rebuild is required.
259
259
- Wnen to back up - After a backup copy of env.list is made, a new backup is needed only if the contents
260
260
of that file changes.
@@ -283,7 +283,7 @@ software runs within. Using a virtual machine adds to resiliency, though it also
283
283
284
284
- How to monitor - Use `docker ps` command to make sure it is running.
285
285
- How to update - See
286
-
[Updates to the Docassemble container](https://suffolklitlab.org/legal-tech-class/docs/practical-guide-docassemble/maintaining-docassemble#updates-to-the-docassemble-container).
286
+
[Updates to the Docassemble container](maintaining-docassemble#updates-to-the-docassemble-container).
287
287
You will use these commands: `docker stop, pull, run,` and `prune`.
288
288
- If you [updated the nginx timeout to 5 minutes](https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/installation/#increase-nginx-timeouts-to-5-minutes)
289
289
earlier, you will need to redo it.
@@ -299,7 +299,7 @@ Playground.
299
299
- How to monitor - If you can get to the Playground, My Interviews, or an individual program, then it's working.
300
300
[UptimeRobot](https://uptimerobot.com/) can be used to receive server up/down notifications by email.
301
301
- How to update - Log in as an administrator. Go to Package Management. Click the "Upgrade" button. See
302
-
[Updates to the Docassemble frontend](https://suffolklitlab.org/legal-tech-class/docs/practical-guide-docassemble/maintaining-docassemble#updates-to-the-docassemble-frontend)
302
+
[Updates to the Docassemble frontend](maintaining-docassemble#updates-to-the-docassemble-frontend)
303
303
- When to update - Every few weeks or as needed if there is a critical bug fix or a desired new feature.
304
304
305
305
### Packages
@@ -308,10 +308,9 @@ These are the program code, frameworks, and utilities that run on the Docassembl
308
308
is an example used by many programs.
309
309
- How to monitor - Monitors like [httpstatus.io](https://httpstatus.io/) or homegrown programs can check if individual
310
310
programs are running. Note: These tools just check whether individual interview pages are reachable. Learn about using
311
-
[ALKiln](https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/alkiln/) to do automated
311
+
[ALKiln](../components/ALKiln/alkiln) to do automated
312
312
start-to-finish testing and monitoring.
313
-
- How to update - You can
314
-
[update Assembly Line packages individually](https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/alkiln/),
315
-
or you can use the [ALDashboard](https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/alkiln/).
313
+
- How to update - You can update Assembly Line packages individually,
314
+
or you can use the [ALDashboard](../components/ALDashboard/overview)
316
315
You can also update individual packages on the Package Management screen.
317
316
- When to update - Every few weeks or as needed if there is a critical bug fix or a desired new feature.
Copy file name to clipboardExpand all lines: docs/archive/bootcamp.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,16 +29,16 @@ If you are finding this page after February 18th, 2021, be sure to watch the vid
29
29
Read:
30
30
31
31
1. If you are unfamiliar with the Assembly Line project, please give the [intro page](../get_started) a look
32
-
1. Read over this short [introduction to Docassemble](https://suffolklitlab.org/legal-tech-class/docs/introduction-to-docassemble)
33
-
1. And if you want more context, consider reading [what should you use Docassemble for?](https://suffolklitlab.org/legal-tech-class/docs/practical-guide-docassemble/practical-guide-docassemble)
32
+
1. Read over this short [introduction to Docassemble](../docassemble_intro/introduction-to-docassemble)
33
+
1. And if you want more context, consider reading [what should you use Docassemble for?](../docassemble_intro/practical-guide-docassemble)
34
34
35
35
Do:
36
36
37
37
After signing up, you should have received invites to our docassemble server (https://apps-dev.suffolklitlab.org) and [our MS TEAMS group](https://teams.microsoft.com/l/channel/19%3a143ac652e7f1494aacda1f6793b21ccc%40thread.tacv2/bootcamp?groupId=eaa9bd9d-cf39-4686-8f30-e55aa9d98c75&tenantId=78733fa9-540e-4eb8-bf29-73c4eeb63412).
38
38
39
39
1. Confirm that you can access the docassemble server and your developer account at https://apps-dev.suffolklitlab.org
40
40
1. Confirm that you can access the [Suffolk LIT Lab Teams group](https://teams.microsoft.com/l/channel/19%3a143ac652e7f1494aacda1f6793b21ccc%40thread.tacv2/bootcamp?groupId=eaa9bd9d-cf39-4686-8f30-e55aa9d98c75&tenantId=78733fa9-540e-4eb8-bf29-73c4eeb63412)
41
-
1.**Optional:** Work through this [Hello, World](https://suffolklitlab.org/legal-tech-class/docs/classes/docacon-2020/hello-world) exercise making use of your developer account. NOTE: this may be challenging for those of you without prior programing experience. You will **NOT** be behind if you can't do it all on your own. Use the [#coding-help](https://teams.microsoft.com/l/channel/19%3ae16e9e9701a5445ea4035b5cb776a4cc%40thread.tacv2/coding-help?groupId=eaa9bd9d-cf39-4686-8f30-e55aa9d98c75&tenantId=78733fa9-540e-4eb8-bf29-73c4eeb63412) channel on Teams if you are stuck and want help.
41
+
1.**Optional:** Work through this [Hello, World](../docassemble_intro/hello-world) exercise making use of your developer account. NOTE: this may be challenging for those of you without prior programing experience. You will **NOT** be behind if you can't do it all on your own. Use the [#coding-help](https://teams.microsoft.com/l/channel/19%3ae16e9e9701a5445ea4035b5cb776a4cc%40thread.tacv2/coding-help?groupId=eaa9bd9d-cf39-4686-8f30-e55aa9d98c75&tenantId=78733fa9-540e-4eb8-bf29-73c4eeb63412) channel on Teams if you are stuck and want help.
42
42
43
43
### Week 1: Introduction and getting started using the Assembly Line interview Weaver, 2/18/2021
Copy file name to clipboardExpand all lines: docs/authoring/customizing_interview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ slug: customizing_interview
9
9
10
10
While the Weaver is a menu-driven, step-by-step process, you'll make further
11
11
edits in the Playground. In the playground, you can directly edit the
12
-
[YAML](https://suffolklitlab.org/legal-tech-class/docs/yaml) text to:
12
+
[YAML](../docassemble_intro/yaml) text to:
13
13
14
14
1. Change the wording of questions
15
15
1. Change the datatype of questions and add show/hide logic
@@ -22,7 +22,7 @@ many changes can be understood by reading the text and then experimenting.
22
22
23
23
This pages offers information about making some common, simple edits.
24
24
You may also want to take this time to read through the materials in
25
-
the [Legal Tech Class](https://suffolklitlab.org/legal-tech-class/docs/introduction-to-docassemble)
25
+
[Introduction to Docassemble](../docassemble_intro/introduction-to-docassemble)
26
26
about the underlying Docassemble platform and how it works.
27
27
28
28
## Double-check that you got things right in the Weaver stage
@@ -135,7 +135,7 @@ you get the name of the user, you would simply switch the order of those 2 lines
135
135
136
136
:::note Learn more about interview order
137
137
This section mentions a bit about interview order, but if you want to learn more,
138
-
you can read it on the [Legal Tech Class](https://suffolklitlab.org/legal-tech-class/docs/practical-guide-docassemble/controlling-interview-order) site.
138
+
you can read it on the [Legal Tech Class](../docassemble_intro/controlling-interview-order) site.
139
139
:::
140
140
141
141
### Order is usually determined by the first variable on the screen
@@ -121,7 +121,7 @@ you should never put a `mandatory` block in the files for each individual docume
121
121
122
122
To group logic that you might want to run with the template it relates to, without making it mandatory:
123
123
124
-
1. use the [`named block` pattern](https://suffolklitlab.org/legal-tech-class/docs/practical-guide-docassemble/controlling-interview-order#triggering-code-and-then-continuing-using-named-blocks) for the `interview order` block
124
+
1. use the [`named block` pattern](../docassemble_intro/controlling-interview-order#triggering-code-and-then-continuing-using-named-blocks) for the `interview order` block
125
125
1. reference your `named block` in a mandatory block inside the `main` file that users will run.
126
126
127
127
While in the development phase, you might want to temporarily test a single document at a time.
0 commit comments