let us replace GIT_BRIDGE_ENABLED=false to GIT_BRIDGE_ENABLED=true.
bin/start
Output:
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.base.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.vars.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.redis.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.mongo.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 3/3
✔ Container redis Started 0.3s
✔ Container mongo Healthy 10.9s
✔ Container sharelatex Started
Despite having in `config/overleaf.rc`:
```
SERVER_PRO=false
```
let us replace `GIT_BRIDGE_ENABLED=false` to `GIT_BRIDGE_ENABLED=true`.
```bash
bin/start
```
<details>
<summary>Output:</summary>
```
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.base.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.vars.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.redis.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /home/benjamin/overleaf-toolkit/lib/docker-compose.mongo.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 3/3
✔ Container redis Started 0.3s
✔ Container mongo Healthy 10.9s
✔ Container sharelatex Started
```
</details>
Related to #7.
```bash
ls data/
```
```
mongo redis sharelatex
```

Assuming changes happening once at a time on the Git and online, this feature could quite easily be implemented by notably leveraging the full history feature.
The official feature has a history differing per person, right? This does not seem wanted.
Assuming changes happening once at a time on the Git and online, this feature could quite easily be implemented by notably leveraging the full history feature.
The official feature has a history differing per person, right? This does not seem wanted.
Salut ! J’ai utilisé ça : https://github.com/JulesColas97/overleaf-sync-plm
J’ai juste testé un peu et il y a eu un bug, et puis j’ai arrêté de l’utiliser. Ce qui m’est arrivé c’est si j’interrompre la synchronisation (e.g. ctrl C) le projet plante, et je ne peux plus restituer la synchro.
Je te conseille de tester cet outil sur un projet de test avant de l’utiliser sur ton projet principal pour ne pas casser ton projet éventuellement.
<details>
<summary>See 31/07/24 internship notes and Slack message to someone maybe having a CLI workaround:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdAaqHXD0v2SNf8n9v8WzLdyDfKBSCyhSqirSYzXT7btFIw
diczViWS+CL/vYH+5BC3msWOX3LW1wRvplI1BpxYmFlGB0JnNuBWiGDVNSFkK0Pq
0oABnAvQnTJTr0nZSYevtJh8duae7qHyqGWJwQkhj5FsUxqhel49VXEBzqM5gejH
Pb+3pCy8XpiLgDKK8i/msmcpIDGDJ9iW0gtNVS6L0APNTsSID81dc2ppcngDsKss
ibzn6XZTr7rfS8FYXNi1Z/ceWF/AkydrqYSE/+92oOORPA==
=6/Dq
-----END PGP MESSAGE-----
```
</details>
He answered me:
> Salut ! J’ai utilisé ça : https://github.com/JulesColas97/overleaf-sync-plm
> J’ai juste testé un peu et il y a eu un bug, et puis j’ai arrêté de l’utiliser. Ce qui m’est arrivé c’est si j’interrompre la synchronisation (e.g. ctrl C) le projet plante, et je ne peux plus restituer la synchro.
> Je te conseille de tester cet outil sur un projet de test avant de l’utiliser sur ton projet principal pour ne pas casser ton projet éventuellement.
Related to [Benjamin_Loison/overleaf-sync/issues](https://codeberg.org/Benjamin_Loison/overleaf-sync/issues).
[moritzgloeckl/overleaf-sync/compare/master...JulesColas97:overleaf-sync-plm:master](https://github.com/moritzgloeckl/overleaf-sync/compare/master...JulesColas97:overleaf-sync-plm:master) looks legitimate, despite being minimized in my opinion see notably [Benjamin_Loison/overleaf-sync/issues/1](https://codeberg.org/Benjamin_Loison/overleaf-sync/issues/1), and [moritzgloeckl/overleaf-sync](https://github.com/moritzgloeckl/overleaf-sync) has 323 stars and last commit was 2 years ago. So should first try in a virtual machine environment. I don't have yet a fork of `overleaf-sync-plm`.
Related to [Improve_websites_thanks_to_open_source/issues/1439](https://codeberg.org/Benjamin_Loison/Improve_websites_thanks_to_open_source/issues/1439).
This feature can be used to have history for other files than the compiled one.
Related to [Benjamin-Loison/gitea/issues/99](https://github.com/Benjamin-Loison/gitea/issues/99).
<details>
<summary>As a workaround can create and update a git when change such another file like:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdAjQ1ueYIzlPQS6hd+2j4Xa07doqQynrPJ1+v9+2xM9R0w
NPJPtoeGsBRy+WunAbd8RVhjrce41JfSdZAOzRJYAAF/rXBnsk5Qbkai9AUBcp6D
0n4BgVnIzJF9INJULt7Ce0+fJL7XANRhlSCQ6rozaNb/Z4USnznIBNdeyu95Gfs6
RcvQAPpmztlC0icpDN0lNr8reTkpK8N1aU4evafILb0rgntHpPPqDWrjMPYttuOW
dNXuRFoTpxYCW3vWej/8zNaMuNzyFylrSJI9knoKW1A=
=KCN6
-----END PGP MESSAGE-----
```
</details>
Related to [Improve_websites_thanks_to_open_source/issues/1543](https://codeberg.org/Benjamin_Loison/Improve_websites_thanks_to_open_source/issues/1543).
[overleaf/overleaf](https://github.com/overleaf/overleaf)
[overleaf/overleaf/forks?sort_by=stargazer_counts](https://github.com/overleaf/overleaf/forks?sort_by=stargazer_counts)
[yu-i-i/overleaf-cep](https://github.com/yu-i-i/overleaf-cep) *CE extended with free premium features*. Has it a public instance? *Caution* in `README` does not seem relevant with *Sandboxed Compiles with TeX Live image selection*, no?
[overleaf-cep/blob/5f27422b3b8def6bdfc5a9fd4c18c45b5dac99ab/README.md#extended-community-edition](https://github.com/yu-i-i/overleaf-cep/blob/5f27422b3b8def6bdfc5a9fd4c18c45b5dac99ab/README.md#extended-community-edition)
The only *git* issue is [yu-i-i/overleaf-cep/issues/58](https://github.com/yu-i-i/overleaf-cep/issues/58) redirecting to [yu-i-i/overleaf-cep/discussions/54](https://github.com/yu-i-i/overleaf-cep/discussions/54) which basically explains that it is hard to deal with feature and it was not managed by the author of this repository.
[yu-i-i/overleaf-cep/issues/40](https://github.com/yu-i-i/overleaf-cep/issues/40) may help.
https://www.overleaf.com/learn/how-to/Git_integration#Known_Limitations should be read.
[ungit](https://github.com/FredrikNoren/ungit) may help.
<details>
<summary>The person:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdARsDe4Pl7dBEpCQrjOFVAyrl6xrhMsy5tY9B54Qgb2m4w
Rij3PuO9adGRIlgurvCRhOyVivi8mMSDj4GW/u6VQqy4PBzqOFk0s/hJCpaV9QaE
1EsBCQIQ/tvFrFfCCVPrUKx873yJE09Mc+dB8zNx3HckGBdjySaqr1JxIib9/s98
stjtxqfWcnGkrE2P5Sm1fDCI9I6VP/0smQAOsQA=
=t5KC
-----END PGP MESSAGE-----
```
</details>
would also be interested in this feature.
[overleaf/overleaf/commit/3476fae7991aca30709ccc413556ad096723eb0c](https://github.com/overleaf/overleaf/commit/3476fae7991aca30709ccc413556ad096723eb0c) mentions multiple Télécom Paris persons.
[overleaf/overleaf/commit/8f360a5add9968ea817b26961a3354bd55ea909d](https://github.com/overleaf/overleaf/commit/8f360a5add9968ea817b26961a3354bd55ea909d) also makes sense.
Note that some commits mention *yu-i-i*, as above.
does not know how to have a git blame like feature to figure out previous changes to a given content.
<details>
<summary>The person:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdAyk0tAqiU01Dvam4TYILGzRHTvI+0/p9V4eg1mcrzEUMw
FbwV75f7X/UPnlrm5Ltto4GpUNHt+WoPYlqFaNcDcz0jLzTtNVCMD3LcMw7ildcs
1E8BCQIQt2mmWHIi23D5fZQRmy/TYUuZqlT++ZkaFvSTxgZzj0J2urUXbWNLPCj0
UzGZRLzzEOcxn+4clZDVcQvmMKkAK1WGW5ANzgM62U2Q
=9zj/
-----END PGP MESSAGE-----
```
</details>
does not know how to have a `git blame` like feature to figure out previous changes to a given content.
recommended me to use this instance also have completion. He uses this instance sometimes, but has not used the Git feature. He is aware of above current issue comment mention about this instance, at least initially he believes that it is a professional instance which I doubt, or at least is not related to the mentioned instance repository.
As far as I know even if it has a perfect Git implementation, can't for current other instance project keep the history by changing the instance, so need a history extraction for the source instance.
<details>
<summary>The instance:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdAla1J+2LWgZ6lSK0lIF00CNhnYbmBtkLgwlFASbWDUzww
hS9NMAzN1l34ptH52AGaxUbDImrItOgX919GiECDRzBihCk+i71yp2UFuT8p/tSp
0lkBR6F19g4DZUzGMpg6W9uFxhse2RPym7+kOQXn123gUrt59S3KRoJ3/wSfZ9Wf
/WX2NyZLCkIv8AOyC/zlOSxs/5sl3cDyzS7Au6TrDXYYcG+0te9OOP/ebA==
=u34o
-----END PGP MESSAGE-----
```
</details>
mentions ShareLaTeX which is from 2017 which is suspicious, source: [Wikipedia: Overleaf#Merge with ShareLaTeX (1322838850)](https://en.wikipedia.org/w/index.php?title=Overleaf&oldid=1322838850#Merge_with_ShareLaTeX).
<details>
<summary>The person:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdArVgzPa/VNpwD93hQg/esOlD3FbMfksaqTLMr7T9n/1gw
lYbuzUZzaxHg+BaaWvkjD4He0itLsXAr6QC1+h3NpfyPZcO/Yn+/LZZGeyVrMjRD
0kIBGB/xsKLD7VTc+2lVvx8Htk4Rje3XRUwuIl5CTNDVU5+GQObnaDMMTc4cVgFw
BOu7HOyIA46BSSgQF3ed3lOwvrY=
=Ijok
-----END PGP MESSAGE-----
```
</details>
recommended me to use this instance also have completion. He uses this instance sometimes, but has not used the Git feature. He is aware of above current issue comment mention about this instance, at least initially he believes that it is a professional instance which I doubt, or at least is not related to the mentioned instance repository.
As far as I know even if it has a perfect Git implementation, can't for current other instance project keep the history by changing the instance, so need a history extraction for the source instance.
do not know how to retrieve history in Git format or search a string in history.
<details>
<summary>The persons:</summary>
```
-----BEGIN PGP MESSAGE-----
hF4DTQa9Wom5MBgSAQdABdf51vbFKgFUJxJ0jFmEPEqRmDYcliuxAj4sh6w3digw
zEhotAS/V0hl2aeGXzYSLVJlTOdKQzM6t+QkZj32udO6X/e/Lj72XHUQ8Rg7i0tU
1JEBCQIQiEac3c1hkzb7tzGHWagM7mhV+/JUljOExqx2M4zXPpB6lU8iUGc7qscY
OxdZArXMP8+F0UMFHiqdHVCWCgbuPo365tE7qpIq8BOlw2jmy5vu8j/BNlLEH4lm
bT4kb52JmAGG6oBU2kX5nFmD1a30ALWv6QsK9wpCm01ICnar4+8oka1dha9Vzlly
MOVc
=Rl/J
-----END PGP MESSAGE-----
```
</details>
do not know how to retrieve history in Git format or search a string in history.
[JulesColas97/overleaf-sync-plm/tree/ad0e6edc0d2f0869a5ec1145a84e6c84c254b531](https://github.com/JulesColas97/overleaf-sync-plm/tree/ad0e6edc0d2f0869a5ec1145a84e6c84c254b531):
```bash
grep -ri 'updates' --exclude-dir=.git
```
does not return anything, hence it does not scrape https://plmlatex.math.cnrs.fr/project/XXXXXXXXXXXXXXXXXXXXXXXX/updates?min_count=10.
labeling history entries, seems to suggest that PLMLaTeX is using old history.
The source does not seem to help more.
https://docs.overleaf.com/on-premises/release-notes/release-notes-3.x.x/full-project-history-migration
Source: [overleaf/overleaf/wiki/Full-Project-History-Migration/5369cc7922c0aca9114abee3da249b40ff5ee63e](https://github.com/overleaf/overleaf/wiki/Full-Project-History-Migration/5369cc7922c0aca9114abee3da249b40ff5ee63e)
labeling history entries, seems to suggest that PLMLaTeX is using old history.
The source does not seem to help more.
is globally the only relevant result which is the server side, so I can only code my script!
DuckDuckGo and Google search `"nextBeforeTimestamp"`.
https://git.fb1.uni-bremen.de/davrot/overleaf-cep/commit/e46decbbcff5c6a5805b810c63d06ce0e30ecca8
is globally the only relevant result which is the server side, so I can only code my script!
DuckDuckGo and Google search "project" "updates" "min_count", "project" "updates" "min_count" "Overleaf" and "project" "updates" "ShareLaTeX" do not seem to help more.
DuckDuckGo and Google search `"project" "updates" "min_count"`, `"project" "updates" "min_count" "Overleaf"` and `"project" "updates" "ShareLaTeX"` do not seem to help more.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Could search overleaf/issues.
Related to #12 and #20.
+46
Despite having in
config/overleaf.rc:let us replace
GIT_BRIDGE_ENABLED=falsetoGIT_BRIDGE_ENABLED=true.Output:
Related to #7.
Assuming changes happening once at a time on the Git and online, this feature could quite easily be implemented by notably leveraging the full history feature.
The official feature has a history differing per person, right? This does not seem wanted.
See 31/07/24 internship notes and Slack message to someone maybe having a CLI workaround:
He answered me:
Related to Benjamin_Loison/overleaf-sync/issues.
Source: https://www.overleaf.com/project/XXXXXXXXXXXXXXXXXXXXXXXX
moritzgloeckl/overleaf-sync/compare/master...JulesColas97:overleaf-sync-plm:master looks legitimate, despite being minimized in my opinion see notably Benjamin_Loison/overleaf-sync/issues/1, and moritzgloeckl/overleaf-sync has 323 stars and last commit was 2 years ago. So should first try in a virtual machine environment. I don't have yet a fork of
overleaf-sync-plm.Experimented successfully
overleaf-sync-plm.Related to Improve_websites_thanks_to_open_source/issues/1439.
This feature can be used to have history for other files than the compiled one.
Related to Benjamin-Loison/gitea/issues/99.
As a workaround can create and update a git when change such another file like:
inotifywaitmay help.Related to Improve_websites_thanks_to_open_source/issues/1543.
overleaf/overleaf
overleaf/overleaf/forks?sort_by=stargazer_counts
yu-i-i/overleaf-cep CE extended with free premium features. Has it a public instance? Caution in
READMEdoes not seem relevant with Sandboxed Compiles with TeX Live image selection, no?overleaf-cep/blob/5f27422b3b8def6bdfc5a9fd4c18c45b5dac99ab/README.md#extended-community-edition
The only git issue is yu-i-i/overleaf-cep/issues/58 redirecting to yu-i-i/overleaf-cep/discussions/54 which basically explains that it is hard to deal with feature and it was not managed by the author of this repository.
yu-i-i/overleaf-cep/issues/40 may help.
https://www.overleaf.com/learn/how-to/Git_integration#Known_Limitations should be read.
ungit may help.
The person:
would also be interested in this feature.
mclegrand/overleaf is by Marc Jeanmougin has 0 stars and last different commit was a month ago.
https://github.com/4llysa/overleaf/issues?q=is%3Aissue mentions Git issues.
Copy SSH key:
overleaf/overleaf/commit/3476fae7991aca30709ccc413556ad096723eb0c mentions multiple Télécom Paris persons.
overleaf/overleaf/commit/8f360a5add9968ea817b26961a3354bd55ea909d also makes sense.
Note that some commits mention yu-i-i, as above.
The person:
does not know how to have a
git blamelike feature to figure out previous changes to a given content.The instance:
mentions ShareLaTeX which is from 2017 which is suspicious, source: Wikipedia: Overleaf#Merge with ShareLaTeX (1322838850).
The person:
recommended me to use this instance also have completion. He uses this instance sometimes, but has not used the Git feature. He is aware of above current issue comment mention about this instance, at least initially he believes that it is a professional instance which I doubt, or at least is not related to the mentioned instance repository.
As far as I know even if it has a perfect Git implementation, can't for current other instance project keep the history by changing the instance, so need a history extraction for the source instance.
Should read
https://forum.math.cnrs.fr/t/synchronisation-git/472
The persons:
do not know how to retrieve history in Git format or search a string in history.
JulesColas97/overleaf-sync-plm/tree/ad0e6edc0d2f0869a5ec1145a84e6c84c254b531:
does not return anything, hence it does not scrape https://plmlatex.math.cnrs.fr/project/XXXXXXXXXXXXXXXXXXXXXXXX/updates?min_count=10.
DuckDuckGo and Google search
"project" "updates" "overleaf" "history".https://docs.overleaf.com/on-premises/release-notes/release-notes-3.x.x/full-project-history-migration
Source: overleaf/overleaf/wiki/Full-Project-History-Migration/5369cc7922c0aca9114abee3da249b40ff5ee63e
labeling history entries, seems to suggest that PLMLaTeX is using old history.
The source does not seem to help more.
DuckDuckGo and Google search
"project" "updates" "before" "Overleaf".Could also search with ShareLaTeX in theory.
DuckDuckGo and Google search
"nextBeforeTimestamp".https://git.fb1.uni-bremen.de/davrot/overleaf-cep/commit/e46decbbcff5c6a5805b810c63d06ce0e30ecca8
is globally the only relevant result which is the server side, so I can only code my script!
Tracked at Benjamin_Loison/Overleaf_history_exporter/issues/2.
DuckDuckGo and Google search
"project" "updates" "min_count","project" "updates" "min_count" "Overleaf"and"project" "updates" "ShareLaTeX"do not seem to help more.