You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by Rod Simpson <ro...@rodsimpson.com> on 2014/03/27 17:52:12 UTC
How can we make it easier for users to try UG?
All,
I have been thinking about ease of use and enabling developer adoption of Usergrid. We need to find a way to enable developers to be up and running with Usergrid in just a few minutes. No compiling, no launcher, no signing up for a 3rd party account. Something hip that the kids will like.
Scenario: Dev in a small shop hears about UG, wants to try it out - maybe on his local machine first, then he will throw it on the LAN for the rest of the devs in the shop to work on.
How can we enable this?
Rod
--
Rod Simpson
@rockerston
rodsimpson.com
Re: How can we make it easier for users to try UG?
Posted by George Reyes <gr...@apigee.com>.
Hi,
Why set the scale at just Dev? I think it would be awesome if we could just
get an average joe/jane to run UG. I feel like the docs do a pretty good
job of telling them how to use it, but it's much harder to explain to
somebody how to set it up.
- George
On Thu, Mar 27, 2014 at 9:52 AM, Rod Simpson <ro...@rodsimpson.com> wrote:
> All,
>
> I have been thinking about ease of use and enabling developer adoption of
> Usergrid. We need to find a way to enable developers to be up and running
> with Usergrid in just a few minutes. No compiling, no launcher, no signing
> up for a 3rd party account. Something hip that the kids will like.
>
> Scenario: Dev in a small shop hears about UG, wants to try it out - maybe
> on his local machine first, then he will throw it on the LAN for the rest
> of the devs in the shop to work on.
>
> How can we enable this?
>
> Rod
>
>
>
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
Re: How can we make it easier for users to try UG?
Posted by Alex Karasulu <ak...@apache.org>.
Hi Rod,
On Thu, Mar 27, 2014 at 8:23 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> Do we have to do an official release before we can offer any of these
> things?
>
>
The Apache UG project would not be able to distribute it without an
official release. However just putting the files to build the brew package,
the docker image and the vagrant file into the git repository does not stop
anyone from building it, using it and publishing it in a distribution
mechanism like docker index or brew. That's not our business, users can use
it as they like even if we don't officially release it. Apache just can't
endorse such actions.
>
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
>
> On March 27, 2014 at 11:13:26 AM, ryan bridges (ryan@fasterness.com)
> wrote:
>
> I actually made a vagrant setup with chef that I use to test things. It
> installs java, tomcat, and cassandra, then clones and builds the stack,
> deploys the .war and sets up the database and superuser. Vagrant forwards
> port 8080 to the host machine so you can play with it on localhost. It
> wouldn't take much to expose more of the configuration of the system to
> chef/vagrant. Take a look and let me know if you think it would be useful.
>
> https://github.com/r3b/usergrid-vagrant
>
> -ryan
>
>
> On Thu, Mar 27, 2014 at 1:05 PM, Todd Nine <tn...@apigee.com> wrote:
>
> > Agreed on the vagrant or docker. I also think adding a brew recipe would
> > be good. It already has all the dependencies available, so we would only
> > have to write the recipe to configure the portal and the webapp.
> >
> >
> > On Thu, Mar 27, 2014 at 9:56 AM, Alex Karasulu <ak...@apache.org>
> > wrote:
> >
> > > On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com>
> wrote:
> > >
> > > > All,
> > > >
> > > > I have been thinking about ease of use and enabling developer
> adoption
> > of
> > > > Usergrid. We need to find a way to enable developers to be up and
> > > running
> > > > with Usergrid in just a few minutes. No compiling, no launcher, no
> > > signing
> > > > up for a 3rd party account. Something hip that the kids will like.
> > > >
> > > > Scenario: Dev in a small shop hears about UG, wants to try it out -
> > maybe
> > > > on his local machine first, then he will throw it on the LAN for the
> > rest
> > > > of the devs in the shop to work on.
> > > >
> > > > How can we enable this?
> > > >
> > >
> > > We should probably include in our git root a docker file and a vagrant
> > file
> > > so people can use docker and or vagrant to immediately build an
> > environment
> > > to work on for dev without cluttering their environment.
> > >
> > > They can also expose the container or vm built by it to other devs to
> > take
> > > a look see.
> > >
> > > --
> > > Best Regards,
> > > -- Alex
> > >
> >
>
--
Best Regards,
-- Alex
Re: How can we make it easier for users to try UG?
Posted by Todd Nine <to...@gmail.com>.
I'm on the fence about this. I'm tempted to say no, but I feel that
even if we don't do an official release, we need to offer our users a
clear migration path. If we push something out based on the 1.0
entity manager/relation manager, then make our first "official"
release with the 2.0 code base, we'll want to offer people a set of
tools for performing the migration. If we can make this easy, (dual
writes with background migration) per release version, I think we'll
be ok. We would just need to provide a clear migration path and
documentation for our users. If you're on 1.0, you MUST go to 2.0.x.
>From 2.0.x, you can upgrade to 2.1.x etc.
Thoughts?
On Thu, Mar 27, 2014 at 11:23 AM, Rod Simpson <ro...@rodsimpson.com> wrote:
> Do we have to do an official release before we can offer any of these things?
>
>
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
>
> On March 27, 2014 at 11:13:26 AM, ryan bridges (ryan@fasterness.com) wrote:
>
> I actually made a vagrant setup with chef that I use to test things. It
> installs java, tomcat, and cassandra, then clones and builds the stack,
> deploys the .war and sets up the database and superuser. Vagrant forwards
> port 8080 to the host machine so you can play with it on localhost. It
> wouldn't take much to expose more of the configuration of the system to
> chef/vagrant. Take a look and let me know if you think it would be useful.
>
> https://github.com/r3b/usergrid-vagrant
>
> -ryan
>
>
> On Thu, Mar 27, 2014 at 1:05 PM, Todd Nine <tn...@apigee.com> wrote:
>
>> Agreed on the vagrant or docker. I also think adding a brew recipe would
>> be good. It already has all the dependencies available, so we would only
>> have to write the recipe to configure the portal and the webapp.
>>
>>
>> On Thu, Mar 27, 2014 at 9:56 AM, Alex Karasulu <ak...@apache.org>
>> wrote:
>>
>> > On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
>> >
>> > > All,
>> > >
>> > > I have been thinking about ease of use and enabling developer adoption
>> of
>> > > Usergrid. We need to find a way to enable developers to be up and
>> > running
>> > > with Usergrid in just a few minutes. No compiling, no launcher, no
>> > signing
>> > > up for a 3rd party account. Something hip that the kids will like.
>> > >
>> > > Scenario: Dev in a small shop hears about UG, wants to try it out -
>> maybe
>> > > on his local machine first, then he will throw it on the LAN for the
>> rest
>> > > of the devs in the shop to work on.
>> > >
>> > > How can we enable this?
>> > >
>> >
>> > We should probably include in our git root a docker file and a vagrant
>> file
>> > so people can use docker and or vagrant to immediately build an
>> environment
>> > to work on for dev without cluttering their environment.
>> >
>> > They can also expose the container or vm built by it to other devs to
>> take
>> > a look see.
>> >
>> > --
>> > Best Regards,
>> > -- Alex
>> >
>>
Re: How can we make it easier for users to try UG?
Posted by Rod Simpson <ro...@rodsimpson.com>.
Do we have to do an official release before we can offer any of these things?
--
Rod Simpson
@rockerston
rodsimpson.com
On March 27, 2014 at 11:13:26 AM, ryan bridges (ryan@fasterness.com) wrote:
I actually made a vagrant setup with chef that I use to test things. It
installs java, tomcat, and cassandra, then clones and builds the stack,
deploys the .war and sets up the database and superuser. Vagrant forwards
port 8080 to the host machine so you can play with it on localhost. It
wouldn't take much to expose more of the configuration of the system to
chef/vagrant. Take a look and let me know if you think it would be useful.
https://github.com/r3b/usergrid-vagrant
-ryan
On Thu, Mar 27, 2014 at 1:05 PM, Todd Nine <tn...@apigee.com> wrote:
> Agreed on the vagrant or docker. I also think adding a brew recipe would
> be good. It already has all the dependencies available, so we would only
> have to write the recipe to configure the portal and the webapp.
>
>
> On Thu, Mar 27, 2014 at 9:56 AM, Alex Karasulu <ak...@apache.org>
> wrote:
>
> > On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> >
> > > All,
> > >
> > > I have been thinking about ease of use and enabling developer adoption
> of
> > > Usergrid. We need to find a way to enable developers to be up and
> > running
> > > with Usergrid in just a few minutes. No compiling, no launcher, no
> > signing
> > > up for a 3rd party account. Something hip that the kids will like.
> > >
> > > Scenario: Dev in a small shop hears about UG, wants to try it out -
> maybe
> > > on his local machine first, then he will throw it on the LAN for the
> rest
> > > of the devs in the shop to work on.
> > >
> > > How can we enable this?
> > >
> >
> > We should probably include in our git root a docker file and a vagrant
> file
> > so people can use docker and or vagrant to immediately build an
> environment
> > to work on for dev without cluttering their environment.
> >
> > They can also expose the container or vm built by it to other devs to
> take
> > a look see.
> >
> > --
> > Best Regards,
> > -- Alex
> >
>
Re: How can we make it easier for users to try UG?
Posted by ryan bridges <ry...@fasterness.com>.
I actually made a vagrant setup with chef that I use to test things. It
installs java, tomcat, and cassandra, then clones and builds the stack,
deploys the .war and sets up the database and superuser. Vagrant forwards
port 8080 to the host machine so you can play with it on localhost. It
wouldn't take much to expose more of the configuration of the system to
chef/vagrant. Take a look and let me know if you think it would be useful.
https://github.com/r3b/usergrid-vagrant
-ryan
On Thu, Mar 27, 2014 at 1:05 PM, Todd Nine <tn...@apigee.com> wrote:
> Agreed on the vagrant or docker. I also think adding a brew recipe would
> be good. It already has all the dependencies available, so we would only
> have to write the recipe to configure the portal and the webapp.
>
>
> On Thu, Mar 27, 2014 at 9:56 AM, Alex Karasulu <ak...@apache.org>
> wrote:
>
> > On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> >
> > > All,
> > >
> > > I have been thinking about ease of use and enabling developer adoption
> of
> > > Usergrid. We need to find a way to enable developers to be up and
> > running
> > > with Usergrid in just a few minutes. No compiling, no launcher, no
> > signing
> > > up for a 3rd party account. Something hip that the kids will like.
> > >
> > > Scenario: Dev in a small shop hears about UG, wants to try it out -
> maybe
> > > on his local machine first, then he will throw it on the LAN for the
> rest
> > > of the devs in the shop to work on.
> > >
> > > How can we enable this?
> > >
> >
> > We should probably include in our git root a docker file and a vagrant
> file
> > so people can use docker and or vagrant to immediately build an
> environment
> > to work on for dev without cluttering their environment.
> >
> > They can also expose the container or vm built by it to other devs to
> take
> > a look see.
> >
> > --
> > Best Regards,
> > -- Alex
> >
>
Re: How can we make it easier for users to try UG?
Posted by Scott Ganyo <sc...@ganyo.com>.
+1 on these. Brew would be great.
On Mar 27, 2014, at 10:05 AM, Todd Nine <tn...@apigee.com> wrote:
> Agreed on the vagrant or docker. I also think adding a brew recipe would
> be good. It already has all the dependencies available, so we would only
> have to write the recipe to configure the portal and the webapp.
>
>
> On Thu, Mar 27, 2014 at 9:56 AM, Alex Karasulu <ak...@apache.org> wrote:
>
>> On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
>>
>>> All,
>>>
>>> I have been thinking about ease of use and enabling developer adoption of
>>> Usergrid. We need to find a way to enable developers to be up and
>> running
>>> with Usergrid in just a few minutes. No compiling, no launcher, no
>> signing
>>> up for a 3rd party account. Something hip that the kids will like.
>>>
>>> Scenario: Dev in a small shop hears about UG, wants to try it out - maybe
>>> on his local machine first, then he will throw it on the LAN for the rest
>>> of the devs in the shop to work on.
>>>
>>> How can we enable this?
>>>
>>
>> We should probably include in our git root a docker file and a vagrant file
>> so people can use docker and or vagrant to immediately build an environment
>> to work on for dev without cluttering their environment.
>>
>> They can also expose the container or vm built by it to other devs to take
>> a look see.
>>
>> --
>> Best Regards,
>> -- Alex
>>
Re: How can we make it easier for users to try UG?
Posted by Todd Nine <tn...@apigee.com>.
Agreed on the vagrant or docker. I also think adding a brew recipe would
be good. It already has all the dependencies available, so we would only
have to write the recipe to configure the portal and the webapp.
On Thu, Mar 27, 2014 at 9:56 AM, Alex Karasulu <ak...@apache.org> wrote:
> On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
>
> > All,
> >
> > I have been thinking about ease of use and enabling developer adoption of
> > Usergrid. We need to find a way to enable developers to be up and
> running
> > with Usergrid in just a few minutes. No compiling, no launcher, no
> signing
> > up for a 3rd party account. Something hip that the kids will like.
> >
> > Scenario: Dev in a small shop hears about UG, wants to try it out - maybe
> > on his local machine first, then he will throw it on the LAN for the rest
> > of the devs in the shop to work on.
> >
> > How can we enable this?
> >
>
> We should probably include in our git root a docker file and a vagrant file
> so people can use docker and or vagrant to immediately build an environment
> to work on for dev without cluttering their environment.
>
> They can also expose the container or vm built by it to other devs to take
> a look see.
>
> --
> Best Regards,
> -- Alex
>
Re: How can we make it easier for users to try UG?
Posted by Alex Karasulu <ak...@apache.org>.
On Thu, Mar 27, 2014 at 6:52 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> All,
>
> I have been thinking about ease of use and enabling developer adoption of
> Usergrid. We need to find a way to enable developers to be up and running
> with Usergrid in just a few minutes. No compiling, no launcher, no signing
> up for a 3rd party account. Something hip that the kids will like.
>
> Scenario: Dev in a small shop hears about UG, wants to try it out - maybe
> on his local machine first, then he will throw it on the LAN for the rest
> of the devs in the shop to work on.
>
> How can we enable this?
>
We should probably include in our git root a docker file and a vagrant file
so people can use docker and or vagrant to immediately build an environment
to work on for dev without cluttering their environment.
They can also expose the container or vm built by it to other devs to take
a look see.
--
Best Regards,
-- Alex