4 ms·

Something which I immediately wondered about is how does this work with backend services when they are required to display part of the app. The FAQ mentions som

by orisho 7y ago

Something which I immediately wondered about is how does this work with backend services when they are required to display part of the app. The FAQ mentions something about environment variables, but is not clear. I would suggest adding a section on that which is accessible outside your app to reduce cognitive load and encourage adoption.

andrethegiant 7y ago
I've added a section in the product FAQs that tries to better address this – does this make it more clear? https://peek.run/l74hv16 https://peek.run/l74hv16
- gingerlime 7y ago
  Not the GP, but had the same question. not sure it’s that clear. So if I have a rails app with a database and redis, how can I use featurepeek?
  - andrethegiant 7y ago
    If your front-end is within rails, you can't really at the moment. We're only focusing on the front-end design/implementation use case right now, so seeding databases etc isn't our priority. If you have your front-end in another project, and use rails only as a backend, you can use environment variables in your front-end to point to rails. That's what we do for our FeaturePeek dashboard app as a matter of fact.
    - orisho 7y ago
      With a couple of educated guesses about how FP works coupled with the FAQ content I'm able to imagine what it looks like, but I think a link to an example project (or even inline if the length makes sense) would go a long way. The key here IMO is something which allows you to passively learn what you'll be required to do to get this to work. My experience is that requiring users to perform an action such as signing up to learn this information will discourage users.
      - andrethegiant 7y ago
        Good point! Our documentation[1] gives lots of examples. Also, our docs repo[2] (Docker/Jenkins) and marketing website[3] (static/CircleCI) are both open source and running on FeaturePeek, so that shows some real-world examples. [1] https://docs.featurepeek.com/intro/ https://docs.featurepeek.com/intro/ [2] https://github.com/featurepeek/documentation https://github.com/featurepeek/documentation [3] https://github.com/featurepeek/marketing-website https://github.com/featurepeek/marketing-website
    - gingerlime 7y ago
      Hmm :( What about loading the commenting and review part onto our own environment? Btw, did you guys talk to dockup? (another YC company I believe)

by orisho 7y ago

andrethegiant 7y ago

I've added a section in the product FAQs that tries to better address this – does this make it more clear? https://peek.run/l74hv16 https://peek.run/l74hv16

gingerlime 7y ago
Not the GP, but had the same question. not sure it’s that clear. So if I have a rails app with a database and redis, how can I use featurepeek?
- andrethegiant 7y ago
  If your front-end is within rails, you can't really at the moment. We're only focusing on the front-end design/implementation use case right now, so seeding databases etc isn't our priority. If you have your front-end in another project, and use rails only as a backend, you can use environment variables in your front-end to point to rails. That's what we do for our FeaturePeek dashboard app as a matter of fact.
  - orisho 7y ago
    With a couple of educated guesses about how FP works coupled with the FAQ content I'm able to imagine what it looks like, but I think a link to an example project (or even inline if the length makes sense) would go a long way. The key here IMO is something which allows you to passively learn what you'll be required to do to get this to work. My experience is that requiring users to perform an action such as signing up to learn this information will discourage users.
    - andrethegiant 7y ago
      Good point! Our documentation[1] gives lots of examples. Also, our docs repo[2] (Docker/Jenkins) and marketing website[3] (static/CircleCI) are both open source and running on FeaturePeek, so that shows some real-world examples. [1] https://docs.featurepeek.com/intro/ https://docs.featurepeek.com/intro/ [2] https://github.com/featurepeek/documentation https://github.com/featurepeek/documentation [3] https://github.com/featurepeek/marketing-website https://github.com/featurepeek/marketing-website
  - gingerlime 7y ago
    Hmm :( What about loading the commenting and review part onto our own environment? Btw, did you guys talk to dockup? (another YC company I believe)