As an add-on to this topic, would it be possible to post an example client configuration for connecting to an instance created by camlistore.org/launch? (e.g., an example client-config.json so one could use camput and have the data be uploaded to the instance created by the launcher). Or perhaps, point me to any existing documentation that says how to do that? It seems like that would be step number two for a lot of users after running the launcher, but I haven't personally been able to figure it out.
On Saturday, April 30, 2016 at 8:24:01 PM UTC-7, Will Norris wrote: > > no editorial type guidance just yet... we haven't really gotten that far. > On the technical side, only thing so far is just to always use relative > URLs in links and always include the file extensions. Both of these are so > that the docs are browsable both on the website and on GitHub. When doc > chnages land in gerrit, they should be live on the website within a > minute. We use blackfriday to parse the markdown, so you can see what all > it supports in terms of markdown syntax. > > On Sat, Apr 30, 2016 at 2:21 PM, clive boulton <[email protected] > <javascript:>> wrote: > >> @willnorris <https://github.com/willnorris> is there a preferred way to >> publish user doc in markdown in the camli source or camli web site? I have >> time and motivation as I often need basic instructions (teach me to >> fish...). >> >> >> On Sat, Apr 30, 2016 at 2:11 PM, David Cittadini <[email protected] >> <javascript:>> wrote: >> >>> Mathieu, thank you for your help :) No, I did something even more >>> stupid, the second time I did not "Add account" on the "Importers - >>> twitter" page. I have no explanation for that.. Anyway, here are the >>> detailed steps for anyone else who needs basic instructions, like I do :) >>> >>> 1. Created a new project called "camlistore" using the Google Cloud >>> Platform Dashboard. >>> 2. Enabled the "Google Compute Engine API >>> <https://console.cloud.google.com/apis/api/compute_component/overview?project=davidcittadini-camlistore-1312>" >>> >>> on the Google Cloud Platform. This is the only API from the list that >>> needs to be enabled, the rest are enabled by default. >>> 3. Entered the Google Project ID into camlistore.org/launch "Google >>> Project ID" field (by copying and pasting the ID) and pressed the "Create >>> instance" button. The "Zone" and "Machine type" were set the defaults. >>> 4. After the instance was created, went to the VM Instances page on >>> Google Cloud Platform to find the "camlistore-server" password (scroll >>> down, it is near the bottom). >>> 5. Went to the IP address specified in the "Camlistore on Google Cloud" >>> message created by camlistore.org/launch (by copying and pasting the >>> address). After logging in, this presented the Camlistore UI and, using >>> the "Server status" menu option on the camlistore UI, I verified that the >>> new instance was "Camlistore: a0276d4f9dff335b7a899fc7952597dadd7d4c80 (on >>> GCE) Go: linux/amd64 go1.6.2, cgo=false". >>> 6. Selected "Importers" from the camlistore UI menu then "twitter" from >>> the web page links, this presented the camlistore "Importers - twitter" >>> page. >>> 7. Went to apps.twitter.com and selected "Create New App". >>> 8. Copied (by using copy and paste) the 4 fields >>> (Name/Description/Website/Callback URL) from the camlistore "Importers - >>> twitter" page to the Twitter "Create an application" page. >>> 9. Selected "Create your Twitter application" button and the Twitter >>> application was created. >>> 10. Selected "manage keys and access tokens" from the Twitter >>> Application Management page for the new Twitter application. >>> 11. Copied (by using copy and paste) the Twitter "Consumer Key (API >>> Key)" field to the camlistore "Client ID" field and copied the >>> Twitter "Consumer Secret (API Secret)" field to the camlistore >>> 12. Pressed the "Save" button on the camlstore "Importer - twitter" page. >>> 13. Selected the "Add account" button under the "Accounts" section on >>> the camlstore "Importer - twitter" page. This will then present the >>> Twitter authorisation page. >>> 14. Selected the Twitter "Authorize app" button. Once authorised in >>> Twitter, you are presented with the camlistore twitter account page. >>> 14. Select the "Start Import" button from the camlistore twitter >>> account page. >>> 15. Pressed the "[<< Back]" link on the the camlistore twitter account >>> page. The Twitter account is now listed as an account under the "Accounts" >>> section. >>> 16. Go back to the camlistore home page. >>> 17. You are now presented with a "twitter account" folder, a "<name> >>> Twitter Account" folder, a "<name> Tweets" folder, a "<name" Twitter Data", >>> a "twitter importer" folder and all your tweets on the camlistore home page. >>> >>> Hope that helps someone.. >>> >>> David >>> >>> On Saturday, April 30, 2016 at 7:43:04 PM UTC+2, mpl wrote: >>>> >>>> I've just tried it from scratch, no problem. >>>> >>>> -created new instance through the launcher >>>> -started right away with configuring a twitter importer >>>> -tweets are showing up in the UI immediately >>>> >>>> dumb question but, did you make sure to redefine the Callback URL in >>>> the twitter app, since you created a new instance which probably has a >>>> different IP from the previous one? >>>> >>>> >>>> On 29 April 2016 at 20:40, David Cittadini <[email protected]> >>>> wrote: >>>> > I have tried the new image (Camlistore: >>>> > a0276d4f9dff335b7a899fc7952597dadd7d4c80 (on GCE) Go: linux/amd64 >>>> go1.6.2, >>>> > cgo=false) and simply created a Twitter Importer, as before . This >>>> time: >>>> > >>>> > 1. The "twitter importer" shows up on the UI, but no tweets. >>>> > >>>> > 2. There is absolutely nothing in the Google Cloud Logging logs, >>>> completely >>>> > zero. >>>> > >>>> > 3. Importer accounts stays as null ("importerAccounts": null) >>>> > >>>> > 4. Uploading an image does not trigger a change. >>>> > >>>> > 5. There are no errors on a "./camtool index". >>>> > >>>> > 6. "WebSocket error - click to reload" shows up a lot on the UI menu. >>>> > >>>> > So, on the new image the Twitter Importer does not seem to work as >>>> > documented.. >>>> > >>>> > >>>> > >>>> > On Friday, April 29, 2016 at 9:10:51 PM UTC+2, mpl wrote: >>>> >> >>>> >> Done. >>>> >> Launcher will now deploy Camlistore rev >>>> >> a0276d4f9dff335b7a899fc7952597dadd7d4c80 built with Go 1.6.2. >>>> >> >>>> >> >>>> >> On 29 April 2016 at 10:51, Mathieu Lonjaret <[email protected]> >>>> wrote: >>>> >> > Yes, that is https://camlistore-review.googlesource.com/6206 >>>> >> > >>>> >> > I'll redeploy the GCE image with this fix in today. >>>> >> > >>>> >> > On 29 April 2016 at 06:26, Brad Fitzpatrick <[email protected]> >>>> wrote: >>>> >> >> It sounds like all three of those problems are the same problem. >>>> >> >> Somehow the >>>> >> >> key isn't getting stored on init. >>>> >> >> >>>> >> >> That sounds like something that Mathieu fixed recently, though. >>>> Maybe >>>> >> >> the >>>> >> >> GCE image wasn't updated? >>>> >> >> >>>> >> >> Mathieu? >>>> >> >> >>>> >> >> >>>> >> >> On Fri, Apr 29, 2016 at 6:57 AM, David Cittadini >>>> >> >> <[email protected]> >>>> >> >> wrote: >>>> >> >>> >>>> >> >>> I have used camlistore.org/launch to create a "standard" >>>> Camlistore >>>> >> >>> implementation on GCE. I have simply followed the instructions >>>> with >>>> >> >>> no >>>> >> >>> additional configuration etc. So far I have found the >>>> following: >>>> >> >>> >>>> >> >>> 1. If I run the Twitter Importer via the UI the log says that >>>> the >>>> >> >>> Twitter >>>> >> >>> account was imported but no tweets show up in the UI. >>>> >> >>> >>>> >> >>> 2. My log is full of error messages that say "error fetching >>>> public >>>> >> >>> key >>>> >> >>> blob sha1<long number>: blob was not fully indexed because of a >>>> >> >>> missing >>>> >> >>> dependency" >>>> >> >>> >>>> >> >>> 3. If I do a "./camtool index" I get errors saying "Destination >>>> needs >>>> >> >>> blob". >>>> >> >>> >>>> >> >>> So, a default "I do not want to think about it or get technical" >>>> >> >>> approach >>>> >> >>> results in a messy implementation where "standard" things do not >>>> see >>>> >> >>> to work >>>> >> >>> how a user would expect - such as one would expect the tweets >>>> just to >>>> >> >>> turn >>>> >> >>> up and that there are no errors... So, should I try and work >>>> through >>>> >> >>> all >>>> >> >>> these errors and work out what is happening or is this all known >>>> and >>>> >> >>> already >>>> >> >>> resolved? Thanks :) >>>> >> >>> >>>> >> >>> -- >>>> >> >>> You received this message because you are subscribed to the >>>> Google >>>> >> >>> Groups >>>> >> >>> "Camlistore" group. >>>> >> >>> To unsubscribe from this group and stop receiving emails from >>>> it, send >>>> >> >>> an >>>> >> >>> email to [email protected]. >>>> >> >>> For more options, visit https://groups.google.com/d/optout. >>>> >> >> >>>> >> >> >>>> >> >> -- >>>> >> >> You received this message because you are subscribed to the >>>> Google >>>> >> >> Groups >>>> >> >> "Camlistore" group. >>>> >> >> To unsubscribe from this group and stop receiving emails from it, >>>> send >>>> >> >> an >>>> >> >> email to [email protected]. >>>> >> >> For more options, visit https://groups.google.com/d/optout. >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> Groups >>>> > "Camlistore" group. >>>> > To unsubscribe from this group and stop receiving emails from it, >>>> send an >>>> > email to [email protected]. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Camlistore" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Camlistore" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
