You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by Sam Ruby <ru...@intertwingly.net> on 2020/04/07 00:56:03 UTC
Re: Porting whimsy to Node.js?
On Mon, Mar 23, 2020 at 3:00 PM Sam Ruby <ru...@intertwingly.net> wrote:
>
> On Thu, Mar 19, 2020 at 9:39 AM Matt Sicker <bo...@gmail.com> wrote:
> >
> > I think making the onboarding experience simpler certainly helps.
>
> Mat, have you had a chance to try the 4 step procedure I linked to?
> Did you have any problems?
It is now up to a six step procedure. though to be fair, the second
step is optional and the first step is now explicit whereas it
previously was implicit.
The code now includes a web server and displays something that is a
close approximation to the board agenda page as well as PMC reports.
Known to work on MacOS and Ubuntu with Firefox or Chrome. Should also
work on Safari or Edge. I don't know of any dependencies which would
preclude it working on Microsoft Windows, and if there are any
problems there, I expect that they can be addressed.
Instructions for MacOS (since that seems to be the most common target
around here):
https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
Current status is included in the second paragraph of the Quick Start section.
- Sam Ruby
Re: Porting whimsy to Node.js?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 6, 2020 at 8:56 PM Sam Ruby <ru...@intertwingly.net> wrote:
>
> On Mon, Mar 23, 2020 at 3:00 PM Sam Ruby <ru...@intertwingly.net> wrote:
> >
> > On Thu, Mar 19, 2020 at 9:39 AM Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > I think making the onboarding experience simpler certainly helps.
> >
> > Mat, have you had a chance to try the 4 step procedure I linked to?
> > Did you have any problems?
>
> It is now up to a six step procedure. though to be fair, the second
> step is optional and the first step is now explicit whereas it
> previously was implicit.
>
> The code now includes a web server and displays something that is a
> close approximation to the board agenda page as well as PMC reports.
>
> Known to work on MacOS and Ubuntu with Firefox or Chrome. Should also
> work on Safari or Edge. I don't know of any dependencies which would
> preclude it working on Microsoft Windows, and if there are any
> problems there, I expect that they can be addressed.
>
> Instructions for MacOS (since that seems to be the most common target
> around here):
>
> https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
>
> Current status is included in the second paragraph of the Quick Start section.
I've made a lot of progress in the past two days. A video
demonstrating the onboarding experience:
https://youtu.be/BQHPzAjI2gI
- Sam Ruby
Re: Porting whimsy to Node.js?
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Patricia Shanahan wrote on 2020-4-20 1:46PM EDT:
> I have two questions:
>
> 1. What should I be learning and practicing to be able to help? It looks
> like JavaScript and React. Is that correct?
Whimsy as a whole is currently primarily Ruby scripts that directly tie
into our records and then produce HTML. Most of the individual tools
are Ruby .cgi scripts, and will stay so.
Sam is porting the Agenda tool itself to Node.js, and simplifying the
architecture along the way. I'm hoping this is the time I'll finally
start really learning JavaScript so I can work on it.
> 2. A couple of days ago I found a web page that gave a couple of docker
> commands for building and running, given a repository clone. I have
> installed docker on my Windows 10 system, and cloned the repository. Now
> I can't find that web page :-(. Link please.
Um, start here: https://github.com/apache/whimsy/
DOCKER.md describes how to setup a whimsy server on your machine,
meaning you can then test out almost anything in the whimsy deployment
locally.
If you're on OSX, then MACOSX.md is a lighter weight way to setup a
local server (i.e. without Docker).
DEVELOPMENT.md are basic setup notes and some specific tweaks to make.
Note that Sam's node.js Agenda work is only in beta now; although if you
want a preview it's super-simple to setup a partially working Agenda:
https://github.com/rubys/whimsy-board-agenda-nodejs
Does that cover it? 8-)
--
- Shane
Whimsy PMC
The Apache Software Foundation
> On 4/20/2020 6:48 AM, Matt Sicker wrote:
>> This is fairly exciting! I’ve never worked on a React application before,
>> but I’ve heard good things. Tooling has only vastly improved since I last
>> looked at it years ago.
>>
>> On Mon, Apr 20, 2020 at 08:37 Sam Ruby <ru...@intertwingly.net> wrote:
>>
>>> On Mon, Apr 20, 2020 at 8:59 AM Roy Lenferink <rl...@apache.org>
>>> wrote:
>>>>
>>>> On 2020/04/20 11:19:38, Sam Ruby <ru...@intertwingly.net> wrote:
>>>>> On Mon, Apr 20, 2020 at 3:23 AM Roy Lenferink <rl...@apache.org>
>>> wrote:
>>>>>>
>>>>>> Hi Sam,
>>>>>>
>>>>>> I was trying to run the nodejs board agenda however it fails to show
>>> the board agenda.
>>>>>> I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
>>>>>>
>>>>>> Running 'yarn dev' returns 'Starting the development server...,
>>> Compiled successfully! & You can
>>>>>> now view node-agenda-app in the browser.'.
>>>>>>
>>>>>> Viewing the board agenda page from the browser the React icon is
>>> spinning with the 'Fetching board
>>>>>> agenda...' text (it did ask to sign in as asf user). The 'Fetching
>>> board agenda...' text doesn't change.
>>>>>>
>>>>>> My terminal shows the following error:
>>>>>> [server] (node:27396) ExperimentalWarning: The fs.promises API is
>>> experimental
>>>>>> [server] TypeError: agenda.matchAll(...) is not a function or its
>>> return value is not iterable
>>>>>> [server] at _default
>>> (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
>>>
>>>>>> [server] at parse
>>> (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
>>>
>>>>>>
>>>>>> The board agenda files are successfully checked out to
>>> work/svn/foundation_board/
>>>>>> Is this something you recognize?
>>>>>
>>>>> What version of node.js are you running?
>>>>
>>>> Well, who would've thought, I was running v10.16.3 :s
>>>> The 'problem' is solved and the 'Agenda' page of the board agenda runs
>>> fine.
>>>>
>>>> This definitely is easy to run; installing Node.js LTS & yarn and
>>>> you're
>>> good to go (centos 8).
>>>>
>>>> Thanks Sam!
>>>
>>> Cool! I've added a minimum version check:
>>>
>>>
>>> https://github.com/rubys/whimsy-board-agenda-nodejs/commit/c023f5af7e7fe9dba1f507dfbd13a88ee2961c09
>>>
>>>
>>> I'm still a week or two away from something minimally useful, largely
>>> because am not merely trying to port this logic, but to have it use
>>> industry standard techniques. I'm replacing my custom event system,
>>> router, and models with React, React Router, and React Redux. The
>>> React Redux change is the one that changes the design the most. It is
>>> also the change that will most make the code approachable by people
>>> coming to this code base.
>>>
>>> I will have a set of pages for developers to view the current state,
>>> contents of caches, etc.
>>>
>>> - Sam Ruby
>>>
>>>
>>>
>>>
>>>>> String.matchAll is a new JavaScript feature[1].
>>>>>
>>>>> Options: we can establish a minimum version of Node.js, I can avoid
>>>>> newish features, or we can use polyfills[2] for such functions.
>>>>>
>>>>>> Roy
>>>>>
>>>>> P.S. Node.js version 14 is scheduled for tomorrow[3]. It is a
>>>>> long-term-support release.
>>>>>
>>>>> [1] https://www.strictmode.io/articles/whats-new-es2020/
>>>>> [2] https://www.npmjs.com/package/string.prototype.matchall
>>>>> [3] https://nodejs.org/en/about/releases/
>>>>>
>>>
>
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Matt Sicker <bo...@gmail.com>.
Without a detailed guide, I'd imagine the Docker method is the most
straightforward. If you try to follow the macOS guide and use
https://chocolatey.org/ instead of homebrew, that might be sufficient
depending on your familiarity with Apache httpd. You can always look
through the setupmymac script in whimsy for ideas on the equivalent
Windows steps.
On Thu, 23 Apr 2020 at 13:21, Patricia Shanahan <pa...@acm.org> wrote:
>
> What is the recommended way of setting up a local Whimsy test
> environment on a Windows 10 computer?
>
> On 4/23/2020 11:03 AM, Matt Sicker wrote:
> > Production doesn't use it, and being a generic CGI in Apache type
> > project, a container is a bit of unnecessary overhead if you don't
> > need it.
> >
> > On Thu, 23 Apr 2020 at 12:58, Patricia Shanahan <pa...@acm.org> wrote:
> >>
> >> On 4/20/2020 6:49 PM, Sam Ruby wrote:
> >>> On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
> >> ...
> >>>> Docker looked to me like a good way of getting a Ubuntu environment for
> >>>> Whimsy development under Windows 10. Is there a better way of doing that?
> >>>
> >>> Given your description, I would suggest that the best match would be:
> >>>
> >>> https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
> >>>
> >>> From my reading, WSL2 is much superior to WSL. At the moment, it is
> >>> available on a pre-release basis. My understanding is that the
> >>> official release will be in May. Ubuntu 20.04 is due to be released
> >>> on Thursday, so if you are setting up a new system, I would be
> >>> inclined to start with that version.
> >>
> >> Unfortunately, wsl-2 is not acceptable for the computer I want to use
> >> for development. It requires installation of an insider-only prerelease
> >> of Window 10, and I use that machine for too many things to consider
> >> anything other than a released version.
> >>
> >> You do not seem to be enthusiastic about Docker. Any particular reasons?
> >>
> >> --
> >> This email has been checked for viruses by AVG.
> >> https://www.avg.com
> >>
> >
> >
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
--
Matt Sicker <bo...@gmail.com>
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
What is the recommended way of setting up a local Whimsy test
environment on a Windows 10 computer?
On 4/23/2020 11:03 AM, Matt Sicker wrote:
> Production doesn't use it, and being a generic CGI in Apache type
> project, a container is a bit of unnecessary overhead if you don't
> need it.
>
> On Thu, 23 Apr 2020 at 12:58, Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/20/2020 6:49 PM, Sam Ruby wrote:
>>> On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
>> ...
>>>> Docker looked to me like a good way of getting a Ubuntu environment for
>>>> Whimsy development under Windows 10. Is there a better way of doing that?
>>>
>>> Given your description, I would suggest that the best match would be:
>>>
>>> https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
>>>
>>> From my reading, WSL2 is much superior to WSL. At the moment, it is
>>> available on a pre-release basis. My understanding is that the
>>> official release will be in May. Ubuntu 20.04 is due to be released
>>> on Thursday, so if you are setting up a new system, I would be
>>> inclined to start with that version.
>>
>> Unfortunately, wsl-2 is not acceptable for the computer I want to use
>> for development. It requires installation of an insider-only prerelease
>> of Window 10, and I use that machine for too many things to consider
>> anything other than a released version.
>>
>> You do not seem to be enthusiastic about Docker. Any particular reasons?
>>
>> --
>> This email has been checked for viruses by AVG.
>> https://www.avg.com
>>
>
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/27/2020 11:26 AM, Sam Ruby wrote:
> On Mon, Apr 27, 2020 at 1:38 PM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> After doing that, how do I start my local Whimsy?
>
> Visit http://whimsy.local/
>
> - Sam Ruby
>
Thanks. I've attached my notes, based on extracts from the e-mails.
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 27, 2020 at 1:38 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> After doing that, how do I start my local Whimsy?
Visit http://whimsy.local/
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Matt Sicker <bo...@gmail.com>.
Don’t we have read only LDAP mirrors? Can’t mess anything there!
On Mon, Apr 27, 2020 at 08:17 Patricia Shanahan <pa...@acm.org> wrote:
>
>
> On 4/24/2020 12:42 PM, Sam Ruby wrote:
> > On Fri, Apr 24, 2020 at 2:43 PM Sam Ruby <ru...@intertwingly.net> wrote:
> >>
> >> This next block will get whimsy installed, but you won't be able to do
> >> much with it until we get a web server up and running, which will be
> >> next.
> >
> > As promised, here is the next block:
> >
> > cd /srv/whimsy
> > rake update svn:update
>
> How long should this step take? I started it yesterday evening and it is
> still running, with no new output in many hours. The last output was:
>
> A Meetings/19980627/rawnotes/manoj/nspr
> A Meetings/19980627/rawnotes/brian/structure.html
> A Meetings/19980627/photos.txt
> A Meetings/20031116/member_proxy.txt
> U Meetings
> Checked out revision 96709.
>
> /srv/svn/apmail_bin
> Authentication realm: <https://svn.apache.org:443> ASF Committers
> Password for 'pats': ********************
>
> U apmail_bin
> Checked out revision 1059839.
> Updating '.archives':
>
>
> > sudo apt install -y apache2 libapache2-mod-passenger
> > sudo sed -i "/localhost$/s/$/ whimsy.local/" /etc/hosts
> > sudo a2enmod authnz_ldap cgid expires headers proxy_http
> > sudo a2enmod proxy proxy_wstunnel rewrite speling
> > sudo cp /srv/whimsy/config/whimsy.conf /etc/apache2/sites-available
> > sudo cp /srv/whimsy/config/25-authz_ldap_group_membership.conf
> > /etc/apache2/conf-available
> > sudo a2ensite whimsy
> > sudo a2enconf 25-authz_ldap_group_membership
> > sudo systemctl restart apache2
> >
> > At this point, you should be able to visit URLs like:
> >
> > http://whimsy.local/
> > http://whimsy.local/test.cgi
> > http://whimsy.local/board/agenda/
> >
> > Now to anticipate your next question, with this you will actually be
> > able to do things like post and approve reports. In other words, if
> > the tool that you try is designed to update svn, it will do so.
> >
> > But I wouldn't recommend that you spend much time with the board
> > agenda tool other than to verify that you can use it to look at
> > agendas. It seems likely at this point that the node.js version of
> > that particular tool is more likely to attract a development
> > community.
> >
> > But what you can do is develop, and test, CGI scripts. If you get
> > something interesting working, submit a pull request so that we can
> > take a look at it.
> >
> > Have fun!
> >
> > - Sam Ruby
> >
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
> --
Matt Sicker <bo...@gmail.com>
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/27/2020 6:36 AM, Sam Ruby wrote:
> On Mon, Apr 27, 2020 at 9:17 AM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/24/2020 12:42 PM, Sam Ruby wrote:
>>> On Fri, Apr 24, 2020 at 2:43 PM Sam Ruby <ru...@intertwingly.net> wrote:
>>>>
>>>> This next block will get whimsy installed, but you won't be able to do
>>>> much with it until we get a web server up and running, which will be
>>>> next.
>>>
>>> As promised, here is the next block:
>>>
>>> cd /srv/whimsy
>>> rake update svn:update
>>
>> How long should this step take? I started it yesterday evening and it is
>> still running, with no new output in many hours. The last output was:
>>
>> A Meetings/19980627/rawnotes/manoj/nspr
>> A Meetings/19980627/rawnotes/brian/structure.html
>> A Meetings/19980627/photos.txt
>> A Meetings/20031116/member_proxy.txt
>> U Meetings
>> Checked out revision 96709.
>>
>> /srv/svn/apmail_bin
>> Authentication realm: <https://svn.apache.org:443> ASF Committers
>> Password for 'pats': ********************
>>
>> U apmail_bin
>> Checked out revision 1059839.
>> Updating '.archives':
>
>
> It should only take seconds. Cancel it and retry?
That seems to have worked. My best guess is that a request for my
password somehow got lost in the output.
After doing that, how do I start my local Whimsy?
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 27, 2020 at 9:17 AM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/24/2020 12:42 PM, Sam Ruby wrote:
> > On Fri, Apr 24, 2020 at 2:43 PM Sam Ruby <ru...@intertwingly.net> wrote:
> >>
> >> This next block will get whimsy installed, but you won't be able to do
> >> much with it until we get a web server up and running, which will be
> >> next.
> >
> > As promised, here is the next block:
> >
> > cd /srv/whimsy
> > rake update svn:update
>
> How long should this step take? I started it yesterday evening and it is
> still running, with no new output in many hours. The last output was:
>
> A Meetings/19980627/rawnotes/manoj/nspr
> A Meetings/19980627/rawnotes/brian/structure.html
> A Meetings/19980627/photos.txt
> A Meetings/20031116/member_proxy.txt
> U Meetings
> Checked out revision 96709.
>
> /srv/svn/apmail_bin
> Authentication realm: <https://svn.apache.org:443> ASF Committers
> Password for 'pats': ********************
>
> U apmail_bin
> Checked out revision 1059839.
> Updating '.archives':
It should only take seconds. Cancel it and retry?
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/24/2020 12:42 PM, Sam Ruby wrote:
> On Fri, Apr 24, 2020 at 2:43 PM Sam Ruby <ru...@intertwingly.net> wrote:
>>
>> This next block will get whimsy installed, but you won't be able to do
>> much with it until we get a web server up and running, which will be
>> next.
>
> As promised, here is the next block:
>
> cd /srv/whimsy
> rake update svn:update
How long should this step take? I started it yesterday evening and it is
still running, with no new output in many hours. The last output was:
A Meetings/19980627/rawnotes/manoj/nspr
A Meetings/19980627/rawnotes/brian/structure.html
A Meetings/19980627/photos.txt
A Meetings/20031116/member_proxy.txt
U Meetings
Checked out revision 96709.
/srv/svn/apmail_bin
Authentication realm: <https://svn.apache.org:443> ASF Committers
Password for 'pats': ********************
U apmail_bin
Checked out revision 1059839.
Updating '.archives':
> sudo apt install -y apache2 libapache2-mod-passenger
> sudo sed -i "/localhost$/s/$/ whimsy.local/" /etc/hosts
> sudo a2enmod authnz_ldap cgid expires headers proxy_http
> sudo a2enmod proxy proxy_wstunnel rewrite speling
> sudo cp /srv/whimsy/config/whimsy.conf /etc/apache2/sites-available
> sudo cp /srv/whimsy/config/25-authz_ldap_group_membership.conf
> /etc/apache2/conf-available
> sudo a2ensite whimsy
> sudo a2enconf 25-authz_ldap_group_membership
> sudo systemctl restart apache2
>
> At this point, you should be able to visit URLs like:
>
> http://whimsy.local/
> http://whimsy.local/test.cgi
> http://whimsy.local/board/agenda/
>
> Now to anticipate your next question, with this you will actually be
> able to do things like post and approve reports. In other words, if
> the tool that you try is designed to update svn, it will do so.
>
> But I wouldn't recommend that you spend much time with the board
> agenda tool other than to verify that you can use it to look at
> agendas. It seems likely at this point that the node.js version of
> that particular tool is more likely to attract a development
> community.
>
> But what you can do is develop, and test, CGI scripts. If you get
> something interesting working, submit a pull request so that we can
> take a look at it.
>
> Have fun!
>
> - Sam Ruby
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/27/2020 3:55 AM, Sam Ruby wrote:
> On Sun, Apr 26, 2020 at 10:08 PM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/24/2020 12:42 PM, Sam Ruby wrote:
>> ...
>>> But what you can do is develop, and test, CGI scripts. If you get
>>> something interesting working, submit a pull request so that we can
>>> take a look at it.
>>>
>>> Have fun!
>>
>> For optimum fun I would like an environment in which I can play freely,
>> with no worries about corrupting production files.
>>
>> There seem to me to be two strategies for getting that. One is to create
>> a simple playpen of my own, with an svn repository and some other toys.
>> The other is a create a fully local Whimsy test environment. That has
>> the advantage that I can play with relevant libraries, as well as basics
>> of Ruby and CGI.
>>
>> What do you think?
>
> That partially depends on what you plan to work on.
>
> If it is a mostly standalone tool that interacts with SVN, I would
> suggest the full local Whimsy environment, just don't implement the
> "svn commit" part yet.
>
> If it is the board agenda tool, I'd suggest taking a look at the
> node.js implementation. By the next board meeting, I'll have a video
> walkthrough.
Although ultimately I want to learn both, I need to pick one of node.js
or Ruby to learn first. As I see it, there are likely to be more
volunteers who already know Javascript, so it would be better for me to
start on the rest of Whimsy, but what do you think?
>
> If it is something that updates LDAP, I don't think you will get very
> far without the existing libraries, so again I would suggest the full
> Whimsy environment. But given that you aren't "root" or in the
> secretarial team, the damage you can do there is very limited.
>
>> --
>> This email has been checked for viruses by AVG.
>> https://www.avg.com
>
> - Sam Ruby
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Sun, Apr 26, 2020 at 10:08 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/24/2020 12:42 PM, Sam Ruby wrote:
> ...
> > But what you can do is develop, and test, CGI scripts. If you get
> > something interesting working, submit a pull request so that we can
> > take a look at it.
> >
> > Have fun!
>
> For optimum fun I would like an environment in which I can play freely,
> with no worries about corrupting production files.
>
> There seem to me to be two strategies for getting that. One is to create
> a simple playpen of my own, with an svn repository and some other toys.
> The other is a create a fully local Whimsy test environment. That has
> the advantage that I can play with relevant libraries, as well as basics
> of Ruby and CGI.
>
> What do you think?
That partially depends on what you plan to work on.
If it is a mostly standalone tool that interacts with SVN, I would
suggest the full local Whimsy environment, just don't implement the
"svn commit" part yet.
If it is the board agenda tool, I'd suggest taking a look at the
node.js implementation. By the next board meeting, I'll have a video
walkthrough.
If it is something that updates LDAP, I don't think you will get very
far without the existing libraries, so again I would suggest the full
Whimsy environment. But given that you aren't "root" or in the
secretarial team, the damage you can do there is very limited.
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/24/2020 12:42 PM, Sam Ruby wrote:
...
> But what you can do is develop, and test, CGI scripts. If you get
> something interesting working, submit a pull request so that we can
> take a look at it.
>
> Have fun!
For optimum fun I would like an environment in which I can play freely,
with no worries about corrupting production files.
There seem to me to be two strategies for getting that. One is to create
a simple playpen of my own, with an svn repository and some other toys.
The other is a create a fully local Whimsy test environment. That has
the advantage that I can play with relevant libraries, as well as basics
of Ruby and CGI.
What do you think?
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Fri, Apr 24, 2020 at 2:43 PM Sam Ruby <ru...@intertwingly.net> wrote:
>
> This next block will get whimsy installed, but you won't be able to do
> much with it until we get a web server up and running, which will be
> next.
As promised, here is the next block:
cd /srv/whimsy
rake update svn:update
sudo apt install -y apache2 libapache2-mod-passenger
sudo sed -i "/localhost$/s/$/ whimsy.local/" /etc/hosts
sudo a2enmod authnz_ldap cgid expires headers proxy_http
sudo a2enmod proxy proxy_wstunnel rewrite speling
sudo cp /srv/whimsy/config/whimsy.conf /etc/apache2/sites-available
sudo cp /srv/whimsy/config/25-authz_ldap_group_membership.conf
/etc/apache2/conf-available
sudo a2ensite whimsy
sudo a2enconf 25-authz_ldap_group_membership
sudo systemctl restart apache2
At this point, you should be able to visit URLs like:
http://whimsy.local/
http://whimsy.local/test.cgi
http://whimsy.local/board/agenda/
Now to anticipate your next question, with this you will actually be
able to do things like post and approve reports. In other words, if
the tool that you try is designed to update svn, it will do so.
But I wouldn't recommend that you spend much time with the board
agenda tool other than to verify that you can use it to look at
agendas. It seems likely at this point that the node.js version of
that particular tool is more likely to attract a development
community.
But what you can do is develop, and test, CGI scripts. If you get
something interesting working, submit a pull request so that we can
take a look at it.
Have fun!
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Fri, Apr 24, 2020 at 1:32 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/24/2020 10:24 AM, Sam Ruby wrote:
> > On Fri, Apr 24, 2020 at 1:02 PM Patricia Shanahan <pa...@acm.org> wrote:
> >>
> >> On 4/24/2020 6:52 AM, Matt Sicker wrote:
> >>> That happened to me on my first run. Try restarting it.
> >>
> >> Thanks. I've tried restarting several times, both with and without
> >> restarting Ubuntu. No luck.
> >
> > I've pushed what may be a fix to this problem. Please pull the latest
> > and try again.
>
> Thanks. That did it. I now see an agenda in my Firefox window.
Cool.
> Before I start playing with my new toy, how much damage can I do? What
> things, if any, do I have to avoid?
You can't do much with it at all at the moment, and everything you can
do is read-only, so worst case is that you bork your VM; and even that
would take some doing.
This next block will get whimsy installed, but you won't be able to do
much with it until we get a web server up and running, which will be
next.
sudo apt-get install -y ruby-dev build-essential libgmp3-dev libldap2-dev
sudo apt-get install -y libsasl2-dev zlib1g-dev imagemagick pdftk ldap-utils
sudo gem install bundler
sudo mkdir -p /srv
sudo chown $(id -u):$(id -g) /srv
cd /srv
git clone https://github.com/apache/whimsy.git
cd whimsy
bundle install
sudo ruby -I lib -r whimsy/asf -e "ASF::LDAP.configure"
At this point, you can verify that you can talk to LDAP with a command
like the following:
ldapsearch -x -LLL uid=pats cn mail
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/24/2020 10:24 AM, Sam Ruby wrote:
> On Fri, Apr 24, 2020 at 1:02 PM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/24/2020 6:52 AM, Matt Sicker wrote:
>>> That happened to me on my first run. Try restarting it.
>>
>> Thanks. I've tried restarting several times, both with and without
>> restarting Ubuntu. No luck.
>
> I've pushed what may be a fix to this problem. Please pull the latest
> and try again.
Thanks. That did it. I now see an agenda in my Firefox window.
Before I start playing with my new toy, how much damage can I do? What
things, if any, do I have to avoid?
>
> I've now install 20.04 so I won't need to guess at what commands might
> work for you. A smaller set of commands that will get you up and
> running from a clean install is as follows:
I'll create a new Ubuntu and try this out.
>
> sudo apt install -y curl git subversion
> curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
> sudo apt install -y nodejs
> sudo npm install -g yarn
> sudo snap install --classic code
>
> git clone https://github.com/rubys/whimsy-board-agenda-nodejs.git
> cd whimsy-board-agenda-nodejs
> yarn install
> yarn dev
>
> I am seeing an error "TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]:
> The feature watch recursively is unavailable on the current platform,
> which is being used to run Node.js" which does not affect the ability
> to see an agenda, but I will look into fixing it.
>
> This afternoon, I will try to collect up commands that will install
> and configure the current (Ruby based) production server.
>
> - Sam Ruby
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Fri, Apr 24, 2020 at 1:02 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/24/2020 6:52 AM, Matt Sicker wrote:
> > That happened to me on my first run. Try restarting it.
>
> Thanks. I've tried restarting several times, both with and without
> restarting Ubuntu. No luck.
I've pushed what may be a fix to this problem. Please pull the latest
and try again.
I've now install 20.04 so I won't need to guess at what commands might
work for you. A smaller set of commands that will get you up and
running from a clean install is as follows:
sudo apt install -y curl git subversion
curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
sudo apt install -y nodejs
sudo npm install -g yarn
sudo snap install --classic code
git clone https://github.com/rubys/whimsy-board-agenda-nodejs.git
cd whimsy-board-agenda-nodejs
yarn install
yarn dev
I am seeing an error "TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]:
The feature watch recursively is unavailable on the current platform,
which is being used to run Node.js" which does not affect the ability
to see an agenda, but I will look into fixing it.
This afternoon, I will try to collect up commands that will install
and configure the current (Ruby based) production server.
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/24/2020 6:52 AM, Matt Sicker wrote:
> That happened to me on my first run. Try restarting it.
Thanks. I've tried restarting several times, both with and without
restarting Ubuntu. No luck.
>
> On Fri, Apr 24, 2020 at 08:35 Patricia Shanahan <pa...@acm.org> wrote:
>
>> On 4/23/2020 8:05 PM, Sam Ruby wrote:
>>> On Thu, Apr 23, 2020 at 10:43 PM Patricia Shanahan <pa...@acm.org> wrote:
>> ...
>>> This is odd. Apparently Ubuntu decided to unbundle npm, requiring you
>>> to install it separately:
>>>
>>> sudo apt install npm
>>>
>>> The next problem is that they are including an old version of node
>>> (10). The current version is 14, and you will need at least 12.
>>>
>>> There is a nifty tool that can help you update node, which you can
>>> install via npm:
>>>
>>> sudo npm install -g n
>>>
>>> Once you have installed n, you can use it to get the latest version of
>> node:
>>>
>>> sudo n latest
>>>
>>> After you do this, verify that you are running a version of node >= 12:
>>>
>>> node --version
>>
>> Not necesssary. sudo -n latest reports the resulting version.
>>
>>>
>>> If you get this far, try yarn dev again.
>>
>> It claims to be listening, and fires up Firefox, but my normal Apache
>> credentials do not work:
>>
>> [server] Error: Command failed: svn checkout
>> https://svn.apache.org/repos/private/foundation/board
>> /home/pats/whimsy-board-agenda-nodejs/work/svn/foundation_board --depth
>> files
>> [server] svn: E170013: Unable to connect to a repository at URL
>> 'https://svn.apache.org/repos/private/foundation/board'
>> [server] svn: E215004: No more credentials or we tried too many times.
>> [server] Authentication failed
>> [server]
>> [server] at ChildProcess.exithandler (child_process.js:303:12)
>> [server] at ChildProcess.emit (events.js:315:20)
>> [server] at maybeClose (internal/child_process.js:1051:16)
>> [server] at Process.ChildProcess._handle.onexit
>> (internal/child_process.js:287:5)
>> [client] Proxy error: Could not proxy request /api/server from
>> localhost:3000 to http://localhost:3001.
>>
>> --
>> This email has been checked for viruses by AVG.
>> https://www.avg.com
>>
>> --
> Matt Sicker <bo...@gmail.com>
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Matt Sicker <bo...@gmail.com>.
That happened to me on my first run. Try restarting it.
On Fri, Apr 24, 2020 at 08:35 Patricia Shanahan <pa...@acm.org> wrote:
> On 4/23/2020 8:05 PM, Sam Ruby wrote:
> > On Thu, Apr 23, 2020 at 10:43 PM Patricia Shanahan <pa...@acm.org> wrote:
> ...
> > This is odd. Apparently Ubuntu decided to unbundle npm, requiring you
> > to install it separately:
> >
> > sudo apt install npm
> >
> > The next problem is that they are including an old version of node
> > (10). The current version is 14, and you will need at least 12.
> >
> > There is a nifty tool that can help you update node, which you can
> > install via npm:
> >
> > sudo npm install -g n
> >
> > Once you have installed n, you can use it to get the latest version of
> node:
> >
> > sudo n latest
> >
> > After you do this, verify that you are running a version of node >= 12:
> >
> > node --version
>
> Not necesssary. sudo -n latest reports the resulting version.
>
> >
> > If you get this far, try yarn dev again.
>
> It claims to be listening, and fires up Firefox, but my normal Apache
> credentials do not work:
>
> [server] Error: Command failed: svn checkout
> https://svn.apache.org/repos/private/foundation/board
> /home/pats/whimsy-board-agenda-nodejs/work/svn/foundation_board --depth
> files
> [server] svn: E170013: Unable to connect to a repository at URL
> 'https://svn.apache.org/repos/private/foundation/board'
> [server] svn: E215004: No more credentials or we tried too many times.
> [server] Authentication failed
> [server]
> [server] at ChildProcess.exithandler (child_process.js:303:12)
> [server] at ChildProcess.emit (events.js:315:20)
> [server] at maybeClose (internal/child_process.js:1051:16)
> [server] at Process.ChildProcess._handle.onexit
> (internal/child_process.js:287:5)
> [client] Proxy error: Could not proxy request /api/server from
> localhost:3000 to http://localhost:3001.
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
> --
Matt Sicker <bo...@gmail.com>
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/23/2020 8:05 PM, Sam Ruby wrote:
> On Thu, Apr 23, 2020 at 10:43 PM Patricia Shanahan <pa...@acm.org> wrote:
...
> This is odd. Apparently Ubuntu decided to unbundle npm, requiring you
> to install it separately:
>
> sudo apt install npm
>
> The next problem is that they are including an old version of node
> (10). The current version is 14, and you will need at least 12.
>
> There is a nifty tool that can help you update node, which you can
> install via npm:
>
> sudo npm install -g n
>
> Once you have installed n, you can use it to get the latest version of node:
>
> sudo n latest
>
> After you do this, verify that you are running a version of node >= 12:
>
> node --version
Not necesssary. sudo -n latest reports the resulting version.
>
> If you get this far, try yarn dev again.
It claims to be listening, and fires up Firefox, but my normal Apache
credentials do not work:
[server] Error: Command failed: svn checkout
https://svn.apache.org/repos/private/foundation/board
/home/pats/whimsy-board-agenda-nodejs/work/svn/foundation_board --depth
files
[server] svn: E170013: Unable to connect to a repository at URL
'https://svn.apache.org/repos/private/foundation/board'
[server] svn: E215004: No more credentials or we tried too many times.
[server] Authentication failed
[server]
[server] at ChildProcess.exithandler (child_process.js:303:12)
[server] at ChildProcess.emit (events.js:315:20)
[server] at maybeClose (internal/child_process.js:1051:16)
[server] at Process.ChildProcess._handle.onexit
(internal/child_process.js:287:5)
[client] Proxy error: Could not proxy request /api/server from
localhost:3000 to http://localhost:3001.
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Apr 23, 2020 at 10:43 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/23/2020 7:14 PM, Sam Ruby wrote:
> ...
> > My bad. Uninstall yarnpkg, and then follow these instructions:
> >
> > https://classic.yarnpkg.com/en/docs/install#debian-stable
> >
> >>> sudo snap install --classic code
> >>> git clone https://github.com/rubys/whimsy-board-agenda-nodejs
> >>> cd whimsy-board-agenda-nodejs
> >>> yarn install
> >>
> >> This is where I got "command not found".
> >>
> >> pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ echo $PATH
> >> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
> >>
> >>> yarn dev
> >>> code .
>
> (I am keeping notes and plan to test them on a clean virtual machine
> once I get this one up.)
Cool!
> Got some warnings from yarn install, and yarn dev failed:
>
> pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ yarn install
> yarn install v1.22.4
> [1/4] Resolving packages...
> [2/4] Fetching packages...
> info fsevents@2.1.2: The platform "linux" is incompatible with this module.
> info "fsevents@2.1.2" is an optional dependency and failed compatibility
> check. Excluding it from installation.
> info fsevents@1.2.12: The platform "linux" is incompatible with this module.
> info "fsevents@1.2.12" is an optional dependency and failed
> compatibility check. Excluding it from installation.
> [3/4] Linking dependencies...
> warning " > @babel/plugin-proposal-class-properties@7.8.3" has unmet
> peer dependency "@babel/core@^7.0.0-0".
> warning "@babel/plugin-proposal-class-properties >
> @babel/helper-create-class-features-plugin@7.8.6" has unmet peer
> dependency "@babel/core@^7.0.0".
> warning " > @babel/register@7.9.0" has unmet peer dependency
> "@babel/core@^7.0.0-0".
> warning " > @testing-library/user-event@7.2.1" has unmet peer dependency
> "@testing-library/dom@>=5".
> warning "react-scripts > @typescript-eslint/eslint-plugin >
> tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >=
> 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >=
> 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
> [4/4] Building fresh packages...
> [1/5] ⠄ core-js-pure
> [2/5] ⠄ dtrace-provider
> [3/5] ⠄ nodemon
> [1/5] ⡀ core-js-pure
> [1/5] ⢀ core-js-pure
> [2/5] ⢀ dtrace-provider
> [1/5] ⠁ core-js-pure
> [-/5] ⠈ waiting...
> [-/5] ⠁ waiting...
> [-/5] ⠂ waiting...
> [2/5] ⠂ dtrace-provider
> Done in 60.09s.
I'm not concerned about any of those warnings.
> pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ yarn dev
> yarn run v1.22.4
> $ NODE_ENV=development concurrently --kill-others-on-fail npm:server
> npm:client
> [server] /bin/sh: 1: npm: not found
> [client] /bin/sh: 1: npm: not found
> [client] npm run client exited with code 127
> --> Sending SIGTERM to other processes..
> [server] npm run server exited with code 127
> error Command failed with exit code 1.
> info Visit https://yarnpkg.com/en/docs/cli/run for documentation about
> this command.
This is odd. Apparently Ubuntu decided to unbundle npm, requiring you
to install it separately:
sudo apt install npm
The next problem is that they are including an old version of node
(10). The current version is 14, and you will need at least 12.
There is a nifty tool that can help you update node, which you can
install via npm:
sudo npm install -g n
Once you have installed n, you can use it to get the latest version of node:
sudo n latest
After you do this, verify that you are running a version of node >= 12:
node --version
If you get this far, try yarn dev again.
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/23/2020 7:14 PM, Sam Ruby wrote:
...
> My bad. Uninstall yarnpkg, and then follow these instructions:
>
> https://classic.yarnpkg.com/en/docs/install#debian-stable
>
>>> sudo snap install --classic code
>>> git clone https://github.com/rubys/whimsy-board-agenda-nodejs
>>> cd whimsy-board-agenda-nodejs
>>> yarn install
>>
>> This is where I got "command not found".
>>
>> pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ echo $PATH
>> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>>
>>> yarn dev
>>> code .
(I am keeping notes and plan to test them on a clean virtual machine
once I get this one up.)
Got some warnings from yarn install, and yarn dev failed:
pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ yarn install
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.1.2: The platform "linux" is incompatible with this module.
info "fsevents@2.1.2" is an optional dependency and failed compatibility
check. Excluding it from installation.
info fsevents@1.2.12: The platform "linux" is incompatible with this module.
info "fsevents@1.2.12" is an optional dependency and failed
compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > @babel/plugin-proposal-class-properties@7.8.3" has unmet
peer dependency "@babel/core@^7.0.0-0".
warning "@babel/plugin-proposal-class-properties >
@babel/helper-create-class-features-plugin@7.8.6" has unmet peer
dependency "@babel/core@^7.0.0".
warning " > @babel/register@7.9.0" has unmet peer dependency
"@babel/core@^7.0.0-0".
warning " > @testing-library/user-event@7.2.1" has unmet peer dependency
"@testing-library/dom@>=5".
warning "react-scripts > @typescript-eslint/eslint-plugin >
tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >=
3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >=
3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
[4/4] Building fresh packages...
[1/5] ⠄ core-js-pure
[2/5] ⠄ dtrace-provider
[3/5] ⠄ nodemon
[1/5] ⡀ core-js-pure
[1/5] ⢀ core-js-pure
[2/5] ⢀ dtrace-provider
[1/5] ⠁ core-js-pure
[-/5] ⠈ waiting...
[-/5] ⠁ waiting...
[-/5] ⠂ waiting...
[2/5] ⠂ dtrace-provider
Done in 60.09s.
pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ yarn dev
yarn run v1.22.4
$ NODE_ENV=development concurrently --kill-others-on-fail npm:server
npm:client
[server] /bin/sh: 1: npm: not found
[client] /bin/sh: 1: npm: not found
[client] npm run client exited with code 127
--> Sending SIGTERM to other processes..
[server] npm run server exited with code 127
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about
this command.
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Apr 23, 2020 at 9:53 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/23/2020 4:34 PM, Sam Ruby wrote:
> > On Thu, Apr 23, 2020 at 6:08 PM Patricia Shanahan <pa...@acm.org> wrote:
> >>
> >> On 4/23/2020 12:51 PM, Patricia Shanahan wrote:
> >>> On 4/23/2020 12:34 PM, Sam Ruby wrote:
> >> ...
> >>>> 3) use a full VM, like VirtualBox, which is free. You should be up
> >>>> and running in minutes. Ubuntu 20.04 came out today, and I will be
> >>>> installing it shortly (first on a dual boot basis on one of my
> >>>> machines, and soon enough as my primary OS on others). I don't expect
> >>>> that you will encounter any VirtualBox specific problems, but if you
> >>>> do, I should be able to reproduce them. Other than that, you will be
> >>>> running on Ubuntu which is my primary development operating system.
> >>>
> >>> It sounds like this is probably the best option.
> >>
> >> I now have a VirtualBox running Ubuntu 20.04.
> >
> > Excellent! You are actually ahead of me.
> >
> >> Microsoft has made some changes that make getting VirtualBox working a
> >> little more complicated than it used to be. Good information can be
> >> found by just searching for the error message with "virtualbox" added.
> >> Do we need to document that sort of thing anywhere, or can we assume any
> >> potential Whimsy developer would know enough to Google an error message?
> >>
> >> I assume I should next try following the Whimsy Ubuntu instructions.
> >
> > Perhaps it might make sense to try the new node version first?
> >
> > sudo apt install nodejs yarnpkg subversion git
>
> The yarnpkg install was successful, but did not put the yarn command in
> my path.
My bad. Uninstall yarnpkg, and then follow these instructions:
https://classic.yarnpkg.com/en/docs/install#debian-stable
> > sudo snap install --classic code
> > git clone https://github.com/rubys/whimsy-board-agenda-nodejs
> > cd whimsy-board-agenda-nodejs
> > yarn install
>
> This is where I got "command not found".
>
> pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>
> > yarn dev
> > code .
> >
> > As to the Ruby version, I'm pretty sure that nobody other than myself
> > has tried the Ubuntu instructions. Since you have a recent Ubuntu, I
> > would recommend ignoring the rbenv and rvm parts of the instructions.
> > But we can work through these together, updating them as we go along,
> > as Ubuntu is both something I use daily and how the server is actually
> > deployed.
> >
> > - Sam Ruby
> >
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/23/2020 4:34 PM, Sam Ruby wrote:
> On Thu, Apr 23, 2020 at 6:08 PM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/23/2020 12:51 PM, Patricia Shanahan wrote:
>>> On 4/23/2020 12:34 PM, Sam Ruby wrote:
>> ...
>>>> 3) use a full VM, like VirtualBox, which is free. You should be up
>>>> and running in minutes. Ubuntu 20.04 came out today, and I will be
>>>> installing it shortly (first on a dual boot basis on one of my
>>>> machines, and soon enough as my primary OS on others). I don't expect
>>>> that you will encounter any VirtualBox specific problems, but if you
>>>> do, I should be able to reproduce them. Other than that, you will be
>>>> running on Ubuntu which is my primary development operating system.
>>>
>>> It sounds like this is probably the best option.
>>
>> I now have a VirtualBox running Ubuntu 20.04.
>
> Excellent! You are actually ahead of me.
>
>> Microsoft has made some changes that make getting VirtualBox working a
>> little more complicated than it used to be. Good information can be
>> found by just searching for the error message with "virtualbox" added.
>> Do we need to document that sort of thing anywhere, or can we assume any
>> potential Whimsy developer would know enough to Google an error message?
>>
>> I assume I should next try following the Whimsy Ubuntu instructions.
>
> Perhaps it might make sense to try the new node version first?
>
> sudo apt install nodejs yarnpkg subversion git
The yarnpkg install was successful, but did not put the yarn command in
my path.
> sudo snap install --classic code
> git clone https://github.com/rubys/whimsy-board-agenda-nodejs
> cd whimsy-board-agenda-nodejs
> yarn install
This is where I got "command not found".
pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
> yarn dev
> code .
>
> As to the Ruby version, I'm pretty sure that nobody other than myself
> has tried the Ubuntu instructions. Since you have a recent Ubuntu, I
> would recommend ignoring the rbenv and rvm parts of the instructions.
> But we can work through these together, updating them as we go along,
> as Ubuntu is both something I use daily and how the server is actually
> deployed.
>
> - Sam Ruby
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Apr 23, 2020 at 6:08 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/23/2020 12:51 PM, Patricia Shanahan wrote:
> > On 4/23/2020 12:34 PM, Sam Ruby wrote:
> ...
> >> 3) use a full VM, like VirtualBox, which is free. You should be up
> >> and running in minutes. Ubuntu 20.04 came out today, and I will be
> >> installing it shortly (first on a dual boot basis on one of my
> >> machines, and soon enough as my primary OS on others). I don't expect
> >> that you will encounter any VirtualBox specific problems, but if you
> >> do, I should be able to reproduce them. Other than that, you will be
> >> running on Ubuntu which is my primary development operating system.
> >
> > It sounds like this is probably the best option.
>
> I now have a VirtualBox running Ubuntu 20.04.
Excellent! You are actually ahead of me.
> Microsoft has made some changes that make getting VirtualBox working a
> little more complicated than it used to be. Good information can be
> found by just searching for the error message with "virtualbox" added.
> Do we need to document that sort of thing anywhere, or can we assume any
> potential Whimsy developer would know enough to Google an error message?
>
> I assume I should next try following the Whimsy Ubuntu instructions.
Perhaps it might make sense to try the new node version first?
sudo apt install nodejs yarnpkg subversion git
sudo snap install --classic code
git clone https://github.com/rubys/whimsy-board-agenda-nodejs
cd whimsy-board-agenda-nodejs
yarn install
yarn dev
code .
As to the Ruby version, I'm pretty sure that nobody other than myself
has tried the Ubuntu instructions. Since you have a recent Ubuntu, I
would recommend ignoring the rbenv and rvm parts of the instructions.
But we can work through these together, updating them as we go along,
as Ubuntu is both something I use daily and how the server is actually
deployed.
- Sam Ruby
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/23/2020 12:51 PM, Patricia Shanahan wrote:
> On 4/23/2020 12:34 PM, Sam Ruby wrote:
...
>> 3) use a full VM, like VirtualBox, which is free. You should be up
>> and running in minutes. Ubuntu 20.04 came out today, and I will be
>> installing it shortly (first on a dual boot basis on one of my
>> machines, and soon enough as my primary OS on others). I don't expect
>> that you will encounter any VirtualBox specific problems, but if you
>> do, I should be able to reproduce them. Other than that, you will be
>> running on Ubuntu which is my primary development operating system.
>
> It sounds like this is probably the best option.
I now have a VirtualBox running Ubuntu 20.04.
Microsoft has made some changes that make getting VirtualBox working a
little more complicated than it used to be. Good information can be
found by just searching for the error message with "virtualbox" added.
Do we need to document that sort of thing anywhere, or can we assume any
potential Whimsy developer would know enough to Google an error message?
I assume I should next try following the Whimsy Ubuntu instructions.
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/23/2020 12:34 PM, Sam Ruby wrote:
> On Thu, Apr 23, 2020 at 1:58 PM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/20/2020 6:49 PM, Sam Ruby wrote:
>>> On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
>> ...
>>>> Docker looked to me like a good way of getting a Ubuntu environment for
>>>> Whimsy development under Windows 10. Is there a better way of doing that?
>>>
>>> Given your description, I would suggest that the best match would be:
>>>
>>> https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
>>>
>>> From my reading, WSL2 is much superior to WSL. At the moment, it is
>>> available on a pre-release basis. My understanding is that the
>>> official release will be in May. Ubuntu 20.04 is due to be released
>>> on Thursday, so if you are setting up a new system, I would be
>>> inclined to start with that version.
>>
>> Unfortunately, wsl-2 is not acceptable for the computer I want to use
>> for development. It requires installation of an insider-only prerelease
>> of Window 10, and I use that machine for too many things to consider
>> anything other than a released version.
>
> My understanding is that wsl-2 will be released as a part of Windows
> 10 version 2004, which is scheduled to be released on May 12/May 13.
>
> https://devblogs.microsoft.com/commandline/wsl2-will-be-generally-available-in-windows-10-version-2004/
> https://thewincentral.com/microsoft-readying-to-launch-windows-10-2004-releases-iso-rtm-build-19041-to-wsus/
>
>> You do not seem to be enthusiastic about Docker. Any particular reasons?
>
> The short answer is: if you wish to create such an environment, I will
> try it out and provide feedback.
>
> Now a longer, a personal perspective. It's a bit raw, please read it as such.
>
> I've had several instances of people saying that they would be willing
> to contribute, but only if I were to build a docker container for
> them. So I did so, at which point they disappeared. Repeat that a
> few times and I hope you can understand why I am less than
> enthusiastic about doing that again.
I do not want to do anything that requires others to do work to get me
started.
>
> I don't use a docker container myself. As Matt points out, we don't
> use docker in production. Things run differently under docker than
> they do natively, or even with a full VM.
>
> My preferred development environment is Ubuntu. Because there are
> enough people who use Macs, I have reproduced that environment on
> macs, and built a script that will create that environment. But I
> personally haven't substantially used Windows for nearly 20 years,
> Nor do any of the other whimsy contributors actively develop on
> windows.
>
> Part of what makes Whimsy development daunting is the substantial
> investment needed in creating a development environment. I'm
> currently working on a version that has substantially less
> requirements. One that I believe should be able to run on any
> environment that can "shell out" to run svn commands. That includes
> WIndows, though I will admit that have not tested it. I was ready to
> test it, only to find out that you wanted an alternative to the
> Windows shell.
>
> So reducing the problem to the core (and please forgive me if I get
> any of this wrong):
>
> 1) You want to develop Whimsy applications on a WIndows 10 machine
> 2) You don't want to use the Windows shell
> 3) Whimsy applications rely on the ability to shell out to commands like "svn".
>
> My recommendations (in order of preference):
>
> 1) I know that this isn't your preference, but consider using the
> windows shell (PowerShell or cmd.exe). If you use an IDE, you won't
> need to use it much, and you can configure your IDE to support
> bash[1]. All you need to be able to do is to run the following
> commands successfully to get started: "git --version", "node
> --version", "svn --version", "code --version", and "yarn --version".
> If you can get those five commands working, you should be able to run
> the node version of the board agenda tool.
>
> 2) use WSL-2, either in inside-only preview mode this month, or wait
> until next month when it it released. It appears to be as close as
> you can get to running a native Ubuntu seamlessly on Windows.
>
> 3) use a full VM, like VirtualBox, which is free. You should be up
> and running in minutes. Ubuntu 20.04 came out today, and I will be
> installing it shortly (first on a dual boot basis on one of my
> machines, and soon enough as my primary OS on others). I don't expect
> that you will encounter any VirtualBox specific problems, but if you
> do, I should be able to reproduce them. Other than that, you will be
> running on Ubuntu which is my primary development operating system.
It sounds like this is probably the best option.
>
> 4) use Docker containers. If you go this route, I will warn you that
> you will need to blaze a trail here. If you have problems, I'm
> willing to help resolve those questions, but it fundamentally will be
> up to you to get it work. I will warn you in advance that if you go
> this route, you will need to become a master of containers, images,
> Dockerfiles, Volumes, Port Forwarding, and likely Docker Compose. An
> example of what you will not be able to do is to run chrome or firefox
> in the container unless you forward your display[2].
Would it make sense to edit the introduction to Whimsy development to
not mention Docker?
>
> I hope this helps, and I apologize in advance if you find any of the
> above offensive.
On the contrary, it looks like valuable technical information.
>
> - Sam Ruby
>
> [1] https://code.visualstudio.com/docs/editor/integrated-terminal#_windows
> [2] https://www.youtube.com/watch?v=CCAK7GhmiEM
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Apr 23, 2020 at 1:58 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/20/2020 6:49 PM, Sam Ruby wrote:
> > On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
> ...
> >> Docker looked to me like a good way of getting a Ubuntu environment for
> >> Whimsy development under Windows 10. Is there a better way of doing that?
> >
> > Given your description, I would suggest that the best match would be:
> >
> > https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
> >
> > From my reading, WSL2 is much superior to WSL. At the moment, it is
> > available on a pre-release basis. My understanding is that the
> > official release will be in May. Ubuntu 20.04 is due to be released
> > on Thursday, so if you are setting up a new system, I would be
> > inclined to start with that version.
>
> Unfortunately, wsl-2 is not acceptable for the computer I want to use
> for development. It requires installation of an insider-only prerelease
> of Window 10, and I use that machine for too many things to consider
> anything other than a released version.
My understanding is that wsl-2 will be released as a part of Windows
10 version 2004, which is scheduled to be released on May 12/May 13.
https://devblogs.microsoft.com/commandline/wsl2-will-be-generally-available-in-windows-10-version-2004/
https://thewincentral.com/microsoft-readying-to-launch-windows-10-2004-releases-iso-rtm-build-19041-to-wsus/
> You do not seem to be enthusiastic about Docker. Any particular reasons?
The short answer is: if you wish to create such an environment, I will
try it out and provide feedback.
Now a longer, a personal perspective. It's a bit raw, please read it as such.
I've had several instances of people saying that they would be willing
to contribute, but only if I were to build a docker container for
them. So I did so, at which point they disappeared. Repeat that a
few times and I hope you can understand why I am less than
enthusiastic about doing that again.
I don't use a docker container myself. As Matt points out, we don't
use docker in production. Things run differently under docker than
they do natively, or even with a full VM.
My preferred development environment is Ubuntu. Because there are
enough people who use Macs, I have reproduced that environment on
macs, and built a script that will create that environment. But I
personally haven't substantially used Windows for nearly 20 years,
Nor do any of the other whimsy contributors actively develop on
windows.
Part of what makes Whimsy development daunting is the substantial
investment needed in creating a development environment. I'm
currently working on a version that has substantially less
requirements. One that I believe should be able to run on any
environment that can "shell out" to run svn commands. That includes
WIndows, though I will admit that have not tested it. I was ready to
test it, only to find out that you wanted an alternative to the
Windows shell.
So reducing the problem to the core (and please forgive me if I get
any of this wrong):
1) You want to develop Whimsy applications on a WIndows 10 machine
2) You don't want to use the Windows shell
3) Whimsy applications rely on the ability to shell out to commands like "svn".
My recommendations (in order of preference):
1) I know that this isn't your preference, but consider using the
windows shell (PowerShell or cmd.exe). If you use an IDE, you won't
need to use it much, and you can configure your IDE to support
bash[1]. All you need to be able to do is to run the following
commands successfully to get started: "git --version", "node
--version", "svn --version", "code --version", and "yarn --version".
If you can get those five commands working, you should be able to run
the node version of the board agenda tool.
2) use WSL-2, either in inside-only preview mode this month, or wait
until next month when it it released. It appears to be as close as
you can get to running a native Ubuntu seamlessly on Windows.
3) use a full VM, like VirtualBox, which is free. You should be up
and running in minutes. Ubuntu 20.04 came out today, and I will be
installing it shortly (first on a dual boot basis on one of my
machines, and soon enough as my primary OS on others). I don't expect
that you will encounter any VirtualBox specific problems, but if you
do, I should be able to reproduce them. Other than that, you will be
running on Ubuntu which is my primary development operating system.
4) use Docker containers. If you go this route, I will warn you that
you will need to blaze a trail here. If you have problems, I'm
willing to help resolve those questions, but it fundamentally will be
up to you to get it work. I will warn you in advance that if you go
this route, you will need to become a master of containers, images,
Dockerfiles, Volumes, Port Forwarding, and likely Docker Compose. An
example of what you will not be able to do is to run chrome or firefox
in the container unless you forward your display[2].
I hope this helps, and I apologize in advance if you find any of the
above offensive.
- Sam Ruby
[1] https://code.visualstudio.com/docs/editor/integrated-terminal#_windows
[2] https://www.youtube.com/watch?v=CCAK7GhmiEM
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Matt Sicker <bo...@gmail.com>.
Production doesn't use it, and being a generic CGI in Apache type
project, a container is a bit of unnecessary overhead if you don't
need it.
On Thu, 23 Apr 2020 at 12:58, Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/20/2020 6:49 PM, Sam Ruby wrote:
> > On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
> ...
> >> Docker looked to me like a good way of getting a Ubuntu environment for
> >> Whimsy development under Windows 10. Is there a better way of doing that?
> >
> > Given your description, I would suggest that the best match would be:
> >
> > https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
> >
> > From my reading, WSL2 is much superior to WSL. At the moment, it is
> > available on a pre-release basis. My understanding is that the
> > official release will be in May. Ubuntu 20.04 is due to be released
> > on Thursday, so if you are setting up a new system, I would be
> > inclined to start with that version.
>
> Unfortunately, wsl-2 is not acceptable for the computer I want to use
> for development. It requires installation of an insider-only prerelease
> of Window 10, and I use that machine for too many things to consider
> anything other than a released version.
>
> You do not seem to be enthusiastic about Docker. Any particular reasons?
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
--
Matt Sicker <bo...@gmail.com>
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/20/2020 6:49 PM, Sam Ruby wrote:
> On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
...
>> Docker looked to me like a good way of getting a Ubuntu environment for
>> Whimsy development under Windows 10. Is there a better way of doing that?
>
> Given your description, I would suggest that the best match would be:
>
> https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
>
> From my reading, WSL2 is much superior to WSL. At the moment, it is
> available on a pre-release basis. My understanding is that the
> official release will be in May. Ubuntu 20.04 is due to be released
> on Thursday, so if you are setting up a new system, I would be
> inclined to start with that version.
Unfortunately, wsl-2 is not acceptable for the computer I want to use
for development. It requires installation of an insider-only prerelease
of Window 10, and I use that machine for too many things to consider
anything other than a released version.
You do not seem to be enthusiastic about Docker. Any particular reasons?
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/20/2020 6:49 PM, Sam Ruby wrote:
> On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
>>
>> On 4/20/2020 3:07 PM, Sam Ruby wrote:
>>> On Mon, Apr 20, 2020 at 1:57 PM Patricia Shanahan <pa...@acm.org> wrote:
>>>
>>> Shane answered based primarily on the current (Ruby) code base. I'll
>>> focus on the node pre-alpha.
>>>
>>>> I have two questions:
>>>>
>>>> 1. What should I be learning and practicing to be able to help? It looks
>>>> like JavaScript and React. Is that correct?
>>>
>>> The most important technologies to focus on are web technologies:
>>> HTML, JavaScript and CSS.
>>
>> I understand HTML, and have done some simple programming in JavaScript.
>> I am not sure I fully understand its object and class model, so I may
>> need to do some more reading in that area. CSS I'll need to learn from
>> scratch.
>
> React applications nominally make use of the JavaScript class and
> object model. Since you mentioned C++ below, you will recognize the
> static keyword. Not much to learn here. It is a dynamic language, so
> you can add do things like add methods to class instances, but you
> won't see much of that either.
>
> The one thing to watch out for is that the rules in JavaScript for
> determining what the value 'this' references take a bit getting used
> to.
'this' is exactly what I need to review.
>
> What is more likely to be new to you is ECMAScript modules:
>
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules
>
>>> While, yes, React would be next, most of it appears theoretical and
>>> daunting. Yet, in practice, it is neither. Most of what you will
>>> need to know is a templating language named JSX.
>>
>> I have a bachelor's degree in mathematics, masters and PhD in computer
>> science, including an A in UCSD's graduate course in theory of
>> computation. It would have to be VERY theoretical to scare me much.
>
> Fair enough. I will say that when I first read the documentation, my
> reaction was along the lines of "why would I ever need that?", and I
> spent the first few years avoiding things that seemed unnecessary.
> I've now learned my lesson, but I will say that seeing the concepts
> applied in a real code base would be much better way to learn the
> concepts than reading the documentation.
I like to work with the combination of a reference document, a tutorial
with exercises, and a body of real code.
>>> https://reactjs.org/docs/introducing-jsx.html
>>> https://reactjs.org/docs/jsx-in-depth.html
>>>
>>> Similarly, Node.js can be learned in a "Just In Time" basis as most of
>>> the application runs in the browser.
>>>
>>>> 2. A couple of days ago I found a web page that gave a couple of docker
>>>> commands for building and running, given a repository clone. I have
>>>> installed docker on my Windows 10 system, and cloned the repository. Now
>>>> I can't find that web page :-(. Link please.
>>>
>>> Shane provided that link, but unless you have a strong reason to want
>>> to use Docker it is just adds to your learning curve.
>>
>> Shane provided a link to what should be a good starting point, and some
>> tips on where to look for information. I have still not found the page
>> I'm looking for.
>
> He pointed to the DOCKER.md page, but I still don't think that's a
> good fit for your use case. See below.
>
>> What I really want is the simplest way of getting to the point of being
>> able to read, modify, and test Whimsy code, preferably in a UNIX-like
>> environment even though I want to use my main home server, a Windows 10
>> machine, for its memory, disk space, backup, and screens.
>>
>> Docker looked to me like a good way of getting a Ubuntu environment for
>> Whimsy development under Windows 10. Is there a better way of doing that?
>
> Given your description, I would suggest that the best match would be:
>
> https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
>
> From my reading, WSL2 is much superior to WSL. At the moment, it is
> available on a pre-release basis. My understanding is that the
> official release will be in May. Ubuntu 20.04 is due to be released
> on Thursday, so if you are setting up a new system, I would be
> inclined to start with that version.
>
> What you will get is a full Ubuntu installation, with a native bash
> shell and Unix filesystem. I haven't tried it myself, but am
> interested in trying it.
>
> https://code.visualstudio.com/remote-tutorials/wsl/getting-started
>
>>> Can I suggest an alternative first task?
>>>
>>> I don't know your background, but given that you have been a
>>> programmer since the 70s, are a Windows 10 user, and are capable of
>>> installing Docker, I presume that you are comfortable with the command
>>> line and doing things like setting %PATH%. Feel free to correct me if
>>> I got this wrong.
>>
>> I am much, much more into programming than systems administration,
>> despite running home computers for the last 40 years. I have programmed
>> professionally in Fortran, C, C++, Forth, Cobol, Verilog, Perl, Java,
>> and a couple of assembly languages. I have written small student or
>> hobby programs in many more languages.
>>
>> I make absolutely minimal use of Powershell, mainly just pasting
>> commands when a process I am following calls for Powershell use. I am
>> familiar with UNIX-like shells and command line tools, and use Cygwin in
>> preference to Powershell wherever possible.
>
> I haven't used Powershell. I did use Cygwin years back, with mixed
> results. I generally still use the command prompt.
I had even forgotten the command prompt exists.
>
>> I'll take a try at that task if you still want me to, understanding it
>> is a poor fit for my skills and experience. I am sure I can learn all
>> the pieces required to do it, but learning a couple of programming
>> languages would be much more fun.
>
> Lets find a setup that works for you, and document it well enough so
> that I and others can reproduce it. I have a variety of machines to
> play with.
I have a Windows 10 machine that I use mainly for video, including Zoom.
I can delete any development tools I have installed there, and work on
making it a Whimsy development box, keeping notes.
>
>>> One thing that would help me help you is if you could document a
>>> Windows 10 equivalent to:
>>>
>>> https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
>>>
>>> Essentially what would be needed is instructions on how to take a bare
>>> Windows machine and install node, yarn, the svn command line client,
>>> and visual studio code.
>>>
>>> If you could create that, that could help others. Additionally, I
>>> have a Windows machine so I can follow along with your instructions
>>> and reproduce any problem you may be seeing.
>>
>>> - Sam Ruby
>>>
>>
>> --
>> This email has been checked for viruses by AVG.
>> https://www.avg.com
>
> - Sam Ruby
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Getting started (Re: Porting whimsy to Node.js?)
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 20, 2020 at 8:38 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> On 4/20/2020 3:07 PM, Sam Ruby wrote:
> > On Mon, Apr 20, 2020 at 1:57 PM Patricia Shanahan <pa...@acm.org> wrote:
> >
> > Shane answered based primarily on the current (Ruby) code base. I'll
> > focus on the node pre-alpha.
> >
> >> I have two questions:
> >>
> >> 1. What should I be learning and practicing to be able to help? It looks
> >> like JavaScript and React. Is that correct?
> >
> > The most important technologies to focus on are web technologies:
> > HTML, JavaScript and CSS.
>
> I understand HTML, and have done some simple programming in JavaScript.
> I am not sure I fully understand its object and class model, so I may
> need to do some more reading in that area. CSS I'll need to learn from
> scratch.
React applications nominally make use of the JavaScript class and
object model. Since you mentioned C++ below, you will recognize the
static keyword. Not much to learn here. It is a dynamic language, so
you can add do things like add methods to class instances, but you
won't see much of that either.
The one thing to watch out for is that the rules in JavaScript for
determining what the value 'this' references take a bit getting used
to.
What is more likely to be new to you is ECMAScript modules:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules
> > While, yes, React would be next, most of it appears theoretical and
> > daunting. Yet, in practice, it is neither. Most of what you will
> > need to know is a templating language named JSX.
>
> I have a bachelor's degree in mathematics, masters and PhD in computer
> science, including an A in UCSD's graduate course in theory of
> computation. It would have to be VERY theoretical to scare me much.
Fair enough. I will say that when I first read the documentation, my
reaction was along the lines of "why would I ever need that?", and I
spent the first few years avoiding things that seemed unnecessary.
I've now learned my lesson, but I will say that seeing the concepts
applied in a real code base would be much better way to learn the
concepts than reading the documentation.
> > https://reactjs.org/docs/introducing-jsx.html
> > https://reactjs.org/docs/jsx-in-depth.html
> >
> > Similarly, Node.js can be learned in a "Just In Time" basis as most of
> > the application runs in the browser.
> >
> >> 2. A couple of days ago I found a web page that gave a couple of docker
> >> commands for building and running, given a repository clone. I have
> >> installed docker on my Windows 10 system, and cloned the repository. Now
> >> I can't find that web page :-(. Link please.
> >
> > Shane provided that link, but unless you have a strong reason to want
> > to use Docker it is just adds to your learning curve.
>
> Shane provided a link to what should be a good starting point, and some
> tips on where to look for information. I have still not found the page
> I'm looking for.
He pointed to the DOCKER.md page, but I still don't think that's a
good fit for your use case. See below.
> What I really want is the simplest way of getting to the point of being
> able to read, modify, and test Whimsy code, preferably in a UNIX-like
> environment even though I want to use my main home server, a Windows 10
> machine, for its memory, disk space, backup, and screens.
>
> Docker looked to me like a good way of getting a Ubuntu environment for
> Whimsy development under Windows 10. Is there a better way of doing that?
Given your description, I would suggest that the best match would be:
https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
From my reading, WSL2 is much superior to WSL. At the moment, it is
available on a pre-release basis. My understanding is that the
official release will be in May. Ubuntu 20.04 is due to be released
on Thursday, so if you are setting up a new system, I would be
inclined to start with that version.
What you will get is a full Ubuntu installation, with a native bash
shell and Unix filesystem. I haven't tried it myself, but am
interested in trying it.
https://code.visualstudio.com/remote-tutorials/wsl/getting-started
> > Can I suggest an alternative first task?
> >
> > I don't know your background, but given that you have been a
> > programmer since the 70s, are a Windows 10 user, and are capable of
> > installing Docker, I presume that you are comfortable with the command
> > line and doing things like setting %PATH%. Feel free to correct me if
> > I got this wrong.
>
> I am much, much more into programming than systems administration,
> despite running home computers for the last 40 years. I have programmed
> professionally in Fortran, C, C++, Forth, Cobol, Verilog, Perl, Java,
> and a couple of assembly languages. I have written small student or
> hobby programs in many more languages.
>
> I make absolutely minimal use of Powershell, mainly just pasting
> commands when a process I am following calls for Powershell use. I am
> familiar with UNIX-like shells and command line tools, and use Cygwin in
> preference to Powershell wherever possible.
I haven't used Powershell. I did use Cygwin years back, with mixed
results. I generally still use the command prompt.
> I'll take a try at that task if you still want me to, understanding it
> is a poor fit for my skills and experience. I am sure I can learn all
> the pieces required to do it, but learning a couple of programming
> languages would be much more fun.
Lets find a setup that works for you, and document it well enough so
that I and others can reproduce it. I have a variety of machines to
play with.
> > One thing that would help me help you is if you could document a
> > Windows 10 equivalent to:
> >
> > https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
> >
> > Essentially what would be needed is instructions on how to take a bare
> > Windows machine and install node, yarn, the svn command line client,
> > and visual studio code.
> >
> > If you could create that, that could help others. Additionally, I
> > have a Windows machine so I can follow along with your instructions
> > and reproduce any problem you may be seeing.
>
> > - Sam Ruby
> >
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
- Sam Ruby
Getting started (Re: Porting whimsy to Node.js?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 4/20/2020 3:07 PM, Sam Ruby wrote:
> On Mon, Apr 20, 2020 at 1:57 PM Patricia Shanahan <pa...@acm.org> wrote:
>
> Shane answered based primarily on the current (Ruby) code base. I'll
> focus on the node pre-alpha.
>
>> I have two questions:
>>
>> 1. What should I be learning and practicing to be able to help? It looks
>> like JavaScript and React. Is that correct?
>
> The most important technologies to focus on are web technologies:
> HTML, JavaScript and CSS.
I understand HTML, and have done some simple programming in JavaScript.
I am not sure I fully understand its object and class model, so I may
need to do some more reading in that area. CSS I'll need to learn from
scratch.
> While, yes, React would be next, most of it appears theoretical and
> daunting. Yet, in practice, it is neither. Most of what you will
> need to know is a templating language named JSX.
I have a bachelor's degree in mathematics, masters and PhD in computer
science, including an A in UCSD's graduate course in theory of
computation. It would have to be VERY theoretical to scare me much.
> https://reactjs.org/docs/introducing-jsx.html
> https://reactjs.org/docs/jsx-in-depth.html
>
> Similarly, Node.js can be learned in a "Just In Time" basis as most of
> the application runs in the browser.
>
>> 2. A couple of days ago I found a web page that gave a couple of docker
>> commands for building and running, given a repository clone. I have
>> installed docker on my Windows 10 system, and cloned the repository. Now
>> I can't find that web page :-(. Link please.
>
> Shane provided that link, but unless you have a strong reason to want
> to use Docker it is just adds to your learning curve.
Shane provided a link to what should be a good starting point, and some
tips on where to look for information. I have still not found the page
I'm looking for.
What I really want is the simplest way of getting to the point of being
able to read, modify, and test Whimsy code, preferably in a UNIX-like
environment even though I want to use my main home server, a Windows 10
machine, for its memory, disk space, backup, and screens.
Docker looked to me like a good way of getting a Ubuntu environment for
Whimsy development under Windows 10. Is there a better way of doing that?
> Can I suggest an alternative first task?
>
> I don't know your background, but given that you have been a
> programmer since the 70s, are a Windows 10 user, and are capable of
> installing Docker, I presume that you are comfortable with the command
> line and doing things like setting %PATH%. Feel free to correct me if
> I got this wrong.
I am much, much more into programming than systems administration,
despite running home computers for the last 40 years. I have programmed
professionally in Fortran, C, C++, Forth, Cobol, Verilog, Perl, Java,
and a couple of assembly languages. I have written small student or
hobby programs in many more languages.
I make absolutely minimal use of Powershell, mainly just pasting
commands when a process I am following calls for Powershell use. I am
familiar with UNIX-like shells and command line tools, and use Cygwin in
preference to Powershell wherever possible.
I'll take a try at that task if you still want me to, understanding it
is a poor fit for my skills and experience. I am sure I can learn all
the pieces required to do it, but learning a couple of programming
languages would be much more fun.
> One thing that would help me help you is if you could document a
> Windows 10 equivalent to:
>
> https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
>
> Essentially what would be needed is instructions on how to take a bare
> Windows machine and install node, yarn, the svn command line client,
> and visual studio code.
>
> If you could create that, that could help others. Additionally, I
> have a Windows machine so I can follow along with your instructions
> and reproduce any problem you may be seeing.
>
> - Sam Ruby
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Porting whimsy to Node.js?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 20, 2020 at 1:57 PM Patricia Shanahan <pa...@acm.org> wrote:
Shane answered based primarily on the current (Ruby) code base. I'll
focus on the node pre-alpha.
> I have two questions:
>
> 1. What should I be learning and practicing to be able to help? It looks
> like JavaScript and React. Is that correct?
The most important technologies to focus on are web technologies:
HTML, JavaScript and CSS.
While, yes, React would be next, most of it appears theoretical and
daunting. Yet, in practice, it is neither. Most of what you will
need to know is a templating language named JSX.
https://reactjs.org/docs/introducing-jsx.html
https://reactjs.org/docs/jsx-in-depth.html
Similarly, Node.js can be learned in a "Just In Time" basis as most of
the application runs in the browser.
> 2. A couple of days ago I found a web page that gave a couple of docker
> commands for building and running, given a repository clone. I have
> installed docker on my Windows 10 system, and cloned the repository. Now
> I can't find that web page :-(. Link please.
Shane provided that link, but unless you have a strong reason to want
to use Docker it is just adds to your learning curve.
Can I suggest an alternative first task?
I don't know your background, but given that you have been a
programmer since the 70s, are a Windows 10 user, and are capable of
installing Docker, I presume that you are comfortable with the command
line and doing things like setting %PATH%. Feel free to correct me if
I got this wrong.
One thing that would help me help you is if you could document a
Windows 10 equivalent to:
https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
Essentially what would be needed is instructions on how to take a bare
Windows machine and install node, yarn, the svn command line client,
and visual studio code.
If you could create that, that could help others. Additionally, I
have a Windows machine so I can follow along with your instructions
and reproduce any problem you may be seeing.
- Sam Ruby
Re: Porting whimsy to Node.js?
Posted by Patricia Shanahan <pa...@acm.org>.
I have two questions:
1. What should I be learning and practicing to be able to help? It looks
like JavaScript and React. Is that correct?
2. A couple of days ago I found a web page that gave a couple of docker
commands for building and running, given a repository clone. I have
installed docker on my Windows 10 system, and cloned the repository. Now
I can't find that web page :-(. Link please.
On 4/20/2020 6:48 AM, Matt Sicker wrote:
> This is fairly exciting! I’ve never worked on a React application before,
> but I’ve heard good things. Tooling has only vastly improved since I last
> looked at it years ago.
>
> On Mon, Apr 20, 2020 at 08:37 Sam Ruby <ru...@intertwingly.net> wrote:
>
>> On Mon, Apr 20, 2020 at 8:59 AM Roy Lenferink <rl...@apache.org>
>> wrote:
>>>
>>> On 2020/04/20 11:19:38, Sam Ruby <ru...@intertwingly.net> wrote:
>>>> On Mon, Apr 20, 2020 at 3:23 AM Roy Lenferink <rl...@apache.org>
>> wrote:
>>>>>
>>>>> Hi Sam,
>>>>>
>>>>> I was trying to run the nodejs board agenda however it fails to show
>> the board agenda.
>>>>> I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
>>>>>
>>>>> Running 'yarn dev' returns 'Starting the development server...,
>> Compiled successfully! & You can
>>>>> now view node-agenda-app in the browser.'.
>>>>>
>>>>> Viewing the board agenda page from the browser the React icon is
>> spinning with the 'Fetching board
>>>>> agenda...' text (it did ask to sign in as asf user). The 'Fetching
>> board agenda...' text doesn't change.
>>>>>
>>>>> My terminal shows the following error:
>>>>> [server] (node:27396) ExperimentalWarning: The fs.promises API is
>> experimental
>>>>> [server] TypeError: agenda.matchAll(...) is not a function or its
>> return value is not iterable
>>>>> [server] at _default
>> (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
>>>>> [server] at parse
>> (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
>>>>>
>>>>> The board agenda files are successfully checked out to
>> work/svn/foundation_board/
>>>>> Is this something you recognize?
>>>>
>>>> What version of node.js are you running?
>>>
>>> Well, who would've thought, I was running v10.16.3 :s
>>> The 'problem' is solved and the 'Agenda' page of the board agenda runs
>> fine.
>>>
>>> This definitely is easy to run; installing Node.js LTS & yarn and you're
>> good to go (centos 8).
>>>
>>> Thanks Sam!
>>
>> Cool! I've added a minimum version check:
>>
>>
>> https://github.com/rubys/whimsy-board-agenda-nodejs/commit/c023f5af7e7fe9dba1f507dfbd13a88ee2961c09
>>
>> I'm still a week or two away from something minimally useful, largely
>> because am not merely trying to port this logic, but to have it use
>> industry standard techniques. I'm replacing my custom event system,
>> router, and models with React, React Router, and React Redux. The
>> React Redux change is the one that changes the design the most. It is
>> also the change that will most make the code approachable by people
>> coming to this code base.
>>
>> I will have a set of pages for developers to view the current state,
>> contents of caches, etc.
>>
>> - Sam Ruby
>>
>>
>>
>>
>>>> String.matchAll is a new JavaScript feature[1].
>>>>
>>>> Options: we can establish a minimum version of Node.js, I can avoid
>>>> newish features, or we can use polyfills[2] for such functions.
>>>>
>>>>> Roy
>>>>
>>>> P.S. Node.js version 14 is scheduled for tomorrow[3]. It is a
>>>> long-term-support release.
>>>>
>>>> [1] https://www.strictmode.io/articles/whats-new-es2020/
>>>> [2] https://www.npmjs.com/package/string.prototype.matchall
>>>> [3] https://nodejs.org/en/about/releases/
>>>>
>>
--
This email has been checked for viruses by AVG.
https://www.avg.com
Re: Porting whimsy to Node.js?
Posted by Matt Sicker <bo...@gmail.com>.
This is fairly exciting! I’ve never worked on a React application before,
but I’ve heard good things. Tooling has only vastly improved since I last
looked at it years ago.
On Mon, Apr 20, 2020 at 08:37 Sam Ruby <ru...@intertwingly.net> wrote:
> On Mon, Apr 20, 2020 at 8:59 AM Roy Lenferink <rl...@apache.org>
> wrote:
> >
> > On 2020/04/20 11:19:38, Sam Ruby <ru...@intertwingly.net> wrote:
> > > On Mon, Apr 20, 2020 at 3:23 AM Roy Lenferink <rl...@apache.org>
> wrote:
> > > >
> > > > Hi Sam,
> > > >
> > > > I was trying to run the nodejs board agenda however it fails to show
> the board agenda.
> > > > I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
> > > >
> > > > Running 'yarn dev' returns 'Starting the development server...,
> Compiled successfully! & You can
> > > > now view node-agenda-app in the browser.'.
> > > >
> > > > Viewing the board agenda page from the browser the React icon is
> spinning with the 'Fetching board
> > > > agenda...' text (it did ask to sign in as asf user). The 'Fetching
> board agenda...' text doesn't change.
> > > >
> > > > My terminal shows the following error:
> > > > [server] (node:27396) ExperimentalWarning: The fs.promises API is
> experimental
> > > > [server] TypeError: agenda.matchAll(...) is not a function or its
> return value is not iterable
> > > > [server] at _default
> (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
> > > > [server] at parse
> (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
> > > >
> > > > The board agenda files are successfully checked out to
> work/svn/foundation_board/
> > > > Is this something you recognize?
> > >
> > > What version of node.js are you running?
> >
> > Well, who would've thought, I was running v10.16.3 :s
> > The 'problem' is solved and the 'Agenda' page of the board agenda runs
> fine.
> >
> > This definitely is easy to run; installing Node.js LTS & yarn and you're
> good to go (centos 8).
> >
> > Thanks Sam!
>
> Cool! I've added a minimum version check:
>
>
> https://github.com/rubys/whimsy-board-agenda-nodejs/commit/c023f5af7e7fe9dba1f507dfbd13a88ee2961c09
>
> I'm still a week or two away from something minimally useful, largely
> because am not merely trying to port this logic, but to have it use
> industry standard techniques. I'm replacing my custom event system,
> router, and models with React, React Router, and React Redux. The
> React Redux change is the one that changes the design the most. It is
> also the change that will most make the code approachable by people
> coming to this code base.
>
> I will have a set of pages for developers to view the current state,
> contents of caches, etc.
>
> - Sam Ruby
>
>
>
>
> > > String.matchAll is a new JavaScript feature[1].
> > >
> > > Options: we can establish a minimum version of Node.js, I can avoid
> > > newish features, or we can use polyfills[2] for such functions.
> > >
> > > > Roy
> > >
> > > P.S. Node.js version 14 is scheduled for tomorrow[3]. It is a
> > > long-term-support release.
> > >
> > > [1] https://www.strictmode.io/articles/whats-new-es2020/
> > > [2] https://www.npmjs.com/package/string.prototype.matchall
> > > [3] https://nodejs.org/en/about/releases/
> > >
>
--
Matt Sicker <bo...@gmail.com>
Re: Porting whimsy to Node.js?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 20, 2020 at 8:59 AM Roy Lenferink <rl...@apache.org> wrote:
>
> On 2020/04/20 11:19:38, Sam Ruby <ru...@intertwingly.net> wrote:
> > On Mon, Apr 20, 2020 at 3:23 AM Roy Lenferink <rl...@apache.org> wrote:
> > >
> > > Hi Sam,
> > >
> > > I was trying to run the nodejs board agenda however it fails to show the board agenda.
> > > I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
> > >
> > > Running 'yarn dev' returns 'Starting the development server..., Compiled successfully! & You can
> > > now view node-agenda-app in the browser.'.
> > >
> > > Viewing the board agenda page from the browser the React icon is spinning with the 'Fetching board
> > > agenda...' text (it did ask to sign in as asf user). The 'Fetching board agenda...' text doesn't change.
> > >
> > > My terminal shows the following error:
> > > [server] (node:27396) ExperimentalWarning: The fs.promises API is experimental
> > > [server] TypeError: agenda.matchAll(...) is not a function or its return value is not iterable
> > > [server] at _default (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
> > > [server] at parse (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
> > >
> > > The board agenda files are successfully checked out to work/svn/foundation_board/
> > > Is this something you recognize?
> >
> > What version of node.js are you running?
>
> Well, who would've thought, I was running v10.16.3 :s
> The 'problem' is solved and the 'Agenda' page of the board agenda runs fine.
>
> This definitely is easy to run; installing Node.js LTS & yarn and you're good to go (centos 8).
>
> Thanks Sam!
Cool! I've added a minimum version check:
https://github.com/rubys/whimsy-board-agenda-nodejs/commit/c023f5af7e7fe9dba1f507dfbd13a88ee2961c09
I'm still a week or two away from something minimally useful, largely
because am not merely trying to port this logic, but to have it use
industry standard techniques. I'm replacing my custom event system,
router, and models with React, React Router, and React Redux. The
React Redux change is the one that changes the design the most. It is
also the change that will most make the code approachable by people
coming to this code base.
I will have a set of pages for developers to view the current state,
contents of caches, etc.
- Sam Ruby
> > String.matchAll is a new JavaScript feature[1].
> >
> > Options: we can establish a minimum version of Node.js, I can avoid
> > newish features, or we can use polyfills[2] for such functions.
> >
> > > Roy
> >
> > P.S. Node.js version 14 is scheduled for tomorrow[3]. It is a
> > long-term-support release.
> >
> > [1] https://www.strictmode.io/articles/whats-new-es2020/
> > [2] https://www.npmjs.com/package/string.prototype.matchall
> > [3] https://nodejs.org/en/about/releases/
> >
Re: Porting whimsy to Node.js?
Posted by Roy Lenferink <rl...@apache.org>.
On 2020/04/20 11:19:38, Sam Ruby <ru...@intertwingly.net> wrote:
> On Mon, Apr 20, 2020 at 3:23 AM Roy Lenferink <rl...@apache.org> wrote:
> >
> > Hi Sam,
> >
> > I was trying to run the nodejs board agenda however it fails to show the board agenda.
> > I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
> >
> > Running 'yarn dev' returns 'Starting the development server..., Compiled successfully! & You can
> > now view node-agenda-app in the browser.'.
> >
> > Viewing the board agenda page from the browser the React icon is spinning with the 'Fetching board
> > agenda...' text (it did ask to sign in as asf user). The 'Fetching board agenda...' text doesn't change.
> >
> > My terminal shows the following error:
> > [server] (node:27396) ExperimentalWarning: The fs.promises API is experimental
> > [server] TypeError: agenda.matchAll(...) is not a function or its return value is not iterable
> > [server] at _default (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
> > [server] at parse (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
> >
> > The board agenda files are successfully checked out to work/svn/foundation_board/
> > Is this something you recognize?
>
> What version of node.js are you running?
>
Well, who would've thought, I was running v10.16.3 :s
The 'problem' is solved and the 'Agenda' page of the board agenda runs fine.
This definitely is easy to run; installing Node.js LTS & yarn and you're good to go (centos 8).
Thanks Sam!
> String.matchAll is a new JavaScript feature[1].
>
> Options: we can establish a minimum version of Node.js, I can avoid
> newish features, or we can use polyfills[2] for such functions.
>
> > Roy
>
> P.S. Node.js version 14 is scheduled for tomorrow[3]. It is a
> long-term-support release.
>
> [1] https://www.strictmode.io/articles/whats-new-es2020/
> [2] https://www.npmjs.com/package/string.prototype.matchall
> [3] https://nodejs.org/en/about/releases/
>
Re: Porting whimsy to Node.js?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Apr 20, 2020 at 3:23 AM Roy Lenferink <rl...@apache.org> wrote:
>
> Hi Sam,
>
> I was trying to run the nodejs board agenda however it fails to show the board agenda.
> I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
>
> Running 'yarn dev' returns 'Starting the development server..., Compiled successfully! & You can
> now view node-agenda-app in the browser.'.
>
> Viewing the board agenda page from the browser the React icon is spinning with the 'Fetching board
> agenda...' text (it did ask to sign in as asf user). The 'Fetching board agenda...' text doesn't change.
>
> My terminal shows the following error:
> [server] (node:27396) ExperimentalWarning: The fs.promises API is experimental
> [server] TypeError: agenda.matchAll(...) is not a function or its return value is not iterable
> [server] at _default (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
> [server] at parse (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
>
> The board agenda files are successfully checked out to work/svn/foundation_board/
> Is this something you recognize?
What version of node.js are you running?
String.matchAll is a new JavaScript feature[1].
Options: we can establish a minimum version of Node.js, I can avoid
newish features, or we can use polyfills[2] for such functions.
> Roy
P.S. Node.js version 14 is scheduled for tomorrow[3]. It is a
long-term-support release.
[1] https://www.strictmode.io/articles/whats-new-es2020/
[2] https://www.npmjs.com/package/string.prototype.matchall
[3] https://nodejs.org/en/about/releases/
Re: Porting whimsy to Node.js?
Posted by Roy Lenferink <rl...@apache.org>.
Hi Sam,
I was trying to run the nodejs board agenda however it fails to show the board agenda.
I am running on CentOS 8 with yarn installed (yarn version 1.22.4).
Running 'yarn dev' returns 'Starting the development server..., Compiled successfully! & You can
now view node-agenda-app in the browser.'.
Viewing the board agenda page from the browser the React icon is spinning with the 'Fetching board
agenda...' text (it did ask to sign in as asf user). The 'Fetching board agenda...' text doesn't change.
My terminal shows the following error:
[server] (node:27396) ExperimentalWarning: The fs.promises API is experimental
[server] TypeError: agenda.matchAll(...) is not a function or its return value is not iterable
[server] at _default (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda/front.js:11:2
[server] at parse (/mnt/projects/asf/whimsy/whimsy-board-agenda-nodejs/src/server/sources/agenda.js:34:5)
The board agenda files are successfully checked out to work/svn/foundation_board/
Is this something you recognize?
Roy
On 2020/04/07 00:56:03, Sam Ruby <ru...@intertwingly.net> wrote:
> On Mon, Mar 23, 2020 at 3:00 PM Sam Ruby <ru...@intertwingly.net> wrote:
> >
> > On Thu, Mar 19, 2020 at 9:39 AM Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > I think making the onboarding experience simpler certainly helps.
> >
> > Mat, have you had a chance to try the 4 step procedure I linked to?
> > Did you have any problems?
>
> It is now up to a six step procedure. though to be fair, the second
> step is optional and the first step is now explicit whereas it
> previously was implicit.
>
> The code now includes a web server and displays something that is a
> close approximation to the board agenda page as well as PMC reports.
>
> Known to work on MacOS and Ubuntu with Firefox or Chrome. Should also
> work on Safari or Edge. I don't know of any dependencies which would
> preclude it working on Microsoft Windows, and if there are any
> problems there, I expect that they can be addressed.
>
> Instructions for MacOS (since that seems to be the most common target
> around here):
>
> https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/MACOSX.md
>
> Current status is included in the second paragraph of the Quick Start section.
>
> - Sam Ruby
>