22 Jan 2017 |
| $Adam invited Github. | 20:29:25 |
| Github joined the room. | 20:29:26 |
| $Adam invited Github [@abeckmeyer:matrix.org] (deprecated). | 20:29:56 |
| Github [@abeckmeyer:matrix.org] (deprecated) joined the room. | 20:30:01 |
| $Adam invited @jbeckmeyer:matrix.org. | 20:31:26 |
| @jbeckmeyer:matrix.org joined the room. | 20:31:38 |
$Adam | So I've chosen the server backend: https://falcon.readthedocs.io | 20:32:54 |
$Adam | And any http request we make to the matrix server will be made with requests | 20:34:31 |
$Adam | I think the only real big thing left to choose as far as implementation details go is what to use for storage. I'm think we just use the filesystem for now and implement SQL if there's a request for it? | 20:35:27 |
$Adam | Thoughts? | 20:35:43 |
@jbeckmeyer:matrix.org | What are the advantages of SQL? | 20:42:26 |
@jbeckmeyer:matrix.org | That would make it worth it for us to work with it | 20:42:41 |
$Adam | If we wanted this app-service to be use on very large homeservers, a database scales better than individual files | 20:46:50 |
$Adam | Doesn't have to be SQL but some form of database other than files would be necessary. | 20:47:37 |
$Adam | In general you get faster access with a database as well. | 20:51:54 |
$Adam | I think you can load an entire database into memory usually. | 20:55:13 |
$Adam | How do you want to govern this project? Any changes must be through a github pull request reviewed by both of us? | 20:57:26 |
$Adam | Or do you want me as the project lead, and I just have to review any changes? | 20:57:44 |
$Adam | Or just ad-hoc either one of us can change anything. | 20:58:08 |
@jbeckmeyer:matrix.org | you should be project lead, since I'm new to python | 20:58:49 |
$Adam | Okay. You have the choice of either working of matrix_relay under your own profile or just working on feature branches from the main repository. | 21:02:55 |
$Adam | You should probably install flake8 for vim. | 21:03:19 |
$Adam | And ipython is nice for working with things really quickly. | 21:05:09 |
$Adam | And that should get you started. Would you like an assignment to work on? | 21:05:12 |
23 Jan 2017 |
| $Adamchanged room power levels. | 08:50:54 |
29 Jan 2017 |
Github [@abeckmeyer:matrix.org] (deprecated) | [non-Jedi/matrix_relay] non-Jedi pushed 2 commits to master: https://github.com/non-Jedi/matrix_relay/commit/e4734811f6cf94054de4967aab2311f19e14d408 non-Jedi: Remove setup.py
setup.py files are not necessary and get in the way for WSGI-style apps. non-Jedi: Add basic logic for /users/{user_id} endpoint | 17:31:38 |
30 Jan 2017 |
Github [@abeckmeyer:matrix.org] (deprecated) | [non-Jedi/matrix_relay] non-Jedi pushed to master: Add gitignore blocking pycache - https://github.com/non-Jedi/matrix_relay/commit/a3219ac94a08f0dd9968426e7325741a0d552937 | 17:31:49 |
31 Jan 2017 |
$Adam | So I've been trying to figure out how we want to do our storage. | 18:26:34 |
$Adam | Redacted or Malformed Event | 18:27:49 |
$Adam | The problem is that we're going to (potentially) have multiple instances of the relay code running at the same time accessing the same data set, and that sets us up for race conditions. | 18:28:11 |