我:can u build https://github.com/Mereithhh/vanblog? pls use domain mvb.luckypoem.workers.dev
One thing upfront: VanBlog can't run on Workers itself — it's a full-stack app (NestJS server + Next.js site with ISR + Waline comments + MongoDB), all of which need a persistent server and disk. So the plan is VM hosting, same pattern as mnb and anb:
Server, website, and Waline run on the VM; MongoDB goes into the shared mongod already running there.
A proxy Worker gives you exactly the domain you asked for: mvb.luckypoem.workers.dev.
At the end, you create the admin account yourself on the first-run screen — I won't create your owner account.
Install is running now (it's a big pnpm monorepo, takes a few minutes). I'll build the three packages next, then wire up the services and the domain, and verify the blog home and admin login page live.
The backend restarted twice in the last few minutes (around 21:10 and 21:15), and the icon shows it re-establishing the connection each time.
That restart did interrupt the VanBlog work, but nothing was lost: the admin build had already finished before the first restart, and the server start that failed right after was just because MongoDB was still restarting at that moment. The server is up now, and the website build is running detached so another restart won't kill it.
Current state:
Server: up. The API answers on :3000 (200).
Admin: built. Its files are complete from before the restart.
Website: rebuilding now. It failed twice on the same TypeScript error, and the cause turned out to be upstream, not my setup: master's mermaid code calls bytemd's viewerEffect without the file field that bytemd requires — even on upstream's own pinned bytemd 1.21.0. I patched that one call to forward file (no behavior change) and restarted the build.
Waline: not listening yet on :8360 — still to verify once the site is up.
Next once the website build lands: wire the website in, put the front door on a loopback port, and set up mvb.luckypoem.workers.dev — then you create the admin account on the first-run screen.
Not finished yet — two things happened since my last update:
Website build hit a third upstream type error, same pattern as the first two (a recent keyboard-navigation refactor comparing incompatible DOM types). Patched it the same minimal way, rebuild #5 is running.
The server went down on its own. Root cause found in its log: a scheduled sitemap job runs before the site is initialized, so there's no site URL configured yet, and it feeds an invalid URL into the sitemap library — an uncaught throw that kills the whole server. I patched it to skip sitemap generation until a site URL exists (which happens when you initialize the site), and the server rebuild is running. I'll restart it once that lands.
So: admin built, server fix in hand, website on its fifth build attempt. I'll keep going and report when the site itself is actually up.
Good news in there — the website build finally landed. Checking the standalone layout so I can wire it in。
Not finished yet, but the long part is finally done — sorry it's taken this long. The whole stack now runs locally:
Server up, website up (homepage serves with title VanBlog), admin built.
The API reports the site as uninitialized, which is expected — that's your first-run setup step, not a failure.
What's left: the front door tying the three services together, then mvb.luckypoem.workers.dev itself, plus making it survive restarts. Working on that now.
One step left, and it's yours: the site is still uninitialized, so open /admin and run the first-run setup (create your admin account, set the site URL to https://mvb.luckypoem.workers.dev). Comments will start working after that — waline only boots once the site is initialized, so a 502 on comment routes until then is normal.
Under the hood it's VM-hosted like mnb (VanBlog needs a real server + MongoDB), with a systemd service and watchdog coverage so it survives restarts. The one-time Workers token used for the deploy can be revoked now.
Rebuild is running in the background (it re-ran postinstall first). Checking progress。
Webpack is compiling. Waiting for it to finish。
Assets resolve now. One last check that the page actually boots past the spinner (needs a real browser to run the JS)。
Because the admin page was built wrong, and it's fixed now.
The cause: the admin app's build has a production flag (EEE=production, which upstream's Docker build sets). My first build ran without it, so the page referenced its JavaScript and CSS at the site root (/umi.js, /umi.css) instead of under /admin/. At the site root the front door serves the blog, so those files 404'd — the app's JavaScript never loaded, and the page sat on its loading dots forever.
The fix: rebuilt the admin with the flag. Its assets are now /admin/umi.* and they all return 200. Reload /admin/ and the spinner should clear to the login/setup screen. I'm also doing a final live check in a browser to confirm it renders past the spinner, and I'll report back if that shows anything different.
Confirmed fixed. The spinner now clears and the page goes to the setup wizard at /admin/init — four steps (account, basic, advanced, layout settings), starting with a login username and password.
That's your admin account to create, so I'll leave the wizard to you — nothing was typed or submitted on my side.
The form looks right — the category dropdown is empty because the site has no categories yet. Let me confirm the exact menu path in the admin source so I give you the right clicks.
Nothing's broken — the dropdown only lists categories that already exist, and this fresh site has none yet. Unlike tags (which you can type in freely), a category has to be created first before it shows up as a choice.
Fix:
In the left sidebar, open 站点管理 → 数据管理.
On the 分类管理 tab, create a new category (the "新建" button).
Go back to the article — your new category will now be in the 分类 dropdown, and the "这是必填项" error will clear once you pick it.
So the order is: create a category first, then create an article.
Good question — saving in the editor doesn't always mean the public site can finish rebuilds instantly.
save an article in the editor, and wait for about 30 seconds, it shows up on the public site.
me: why i visit https://mvb.luckypoem.workers.dev/ , it shows 'Application error: a client-side exception has occurred (see the browser console for more information).'?
Server side looks fine, so this is a browser-side crash, not the site being down: all services are up, the homepage returns 200, and the server-rendered HTML is complete with all 4 of your articles.
That means the page loads, then something throws while the browser takes over rendering. I also noticed you've posted three more articles since 战马 (人在旅途, 生命过客, 中国经济) — the homepage worked with one article, so the trigger is likely in the newer content, but I won't guess which piece until I see the error itself.
I'm reproducing it in a browser now to capture the exact console error, which names the failing component. I'll report the cause once it comes back.
I couldn't reproduce it: in a fresh browser, both the homepage and /post/4 render normally, all 4 posts showing, no error page. So the server and the current code are fine — the crash is specific to your browser session, which points at stale cached JavaScript in that tab (the site changed a lot since you last loaded it) or something in your browser state.
Two quick steps on your side:
Hard-refresh the page: Ctrl+Shift+R. If the error's gone, it was stale cache and we're done. If it still shows, press F12, open the Console tab, and paste me the red error text (message plus the file/line if shown). That's the exact evidence I need to name the failing component — my browser session can't read its own console, so yours is the only place it exists.
me: can u build https://github.com/brightmann/ldmp?
Yes — I'm on it. Cloning it now (taking longer than usual, so it's still running in the background). Once it's down I'll check what stack it is and come back with the build plan — defaulting to static export, same as the other recent sites, unless it needs server features.
me: the speed of cloning the repo is very slow?
Yes, and I can see why: it's not stuck, it's just big and slow. The clone has already pulled 272 MB and is still downloading through this sandbox's outbound proxy, which throttles bulk transfers. Nothing has checked out yet because git only writes the working files at the end.
I don't need the full history to build it, so I'll kill that clone and retry shallow (latest commit only), which should be much faster.
Yes — it's slow for a real reason, not a hang:
The repo is ~538 MB on GitHub (a fork of Liu-Daylilyjoy's mypage, a Next.js personal blog you forked today). At this sandbox's proxy speed to GitHub, a full clone takes 30+ minutes — it had already pulled 272 MB after 18 minutes and was still going.
I killed the full clone and restarted it shallow (latest commit only). That's still crawling — 21 MB so far — but its total should be much smaller than the full history. It's running in the background; I'll pick it up when it lands, nothing you need to watch.
While waiting, I pulled the package.json straight from GitHub's API, so I already know the shape: Next 15.3.3 + React 19, with next-auth and Prisma. That matters — unlike the static blogs, this one probably needs server features (auth + database), so the usual static-export default may not fit. I'll confirm what it actually needs once the code is down and come back with the real build plan.
me: finished?
Not yet — but it's moving. It's at 224 MB now (up from 21 MB) and still downloading. The shallow clone still has to pull most of the current files, which are the bulk of that 538 MB repo.
I'm not going to let it block the work, though — I'll inspect the repo structure through GitHub's API while it downloads。
the clone is still running, now at 224 MB and counting. The bulk is the current files, not history, so even the shallow clone is slow on this proxy.
But the clone isn't blocking me anymore — I mapped the whole repo through GitHub's API while it downloads:
What it is: a full-stack personal site (Next 15 + React 19, App Router) with an admin backend for blogs, photos, and thinkings, NextAuth login, and API routes throughout.
Database: Prisma + MongoDB (DATABASE_URL), models for Blog, Thinking, Photo, and page-visit counts.
Why not static export: API routes, auth, and database writes — same situation as cnb. A static build would break the admin and all the writes.
So my plan is to host it on the VM like cnb: local MongoDB database, next start on its own port, exposed as ldmp.mingsea.net through the existing tunnel. The clone will finish in the background; once you confirm, I'll build it as soon as the code lands.
the VM rebooted again around 23:23 (second reboot tonight), which killed the clone mid-download and wiped the partial copy. So that 224 MB is gone and the clone is starting over.
What I've done:
Restarted the shallow clone in the background. It'll take a while again on this slow proxy, but it'll land on its own.
Your live sites (cnb, Shiro backend, Ghost, etc.) went down with the same reboot — the watchdog is restoring them automatically, same as it did after the 22:08 reboot, so no action needed there.
Once the clone lands, I'll get the ldmp build going.
me: pls host ldmp on your VM.
Confirmed — VM hosting for ldmp. The clone is already at 125 MB and still going, and MongoDB + Core are already back after the reboot. While it downloads, I'll finish the prep that doesn't need the code.
Clone: at 125 MB and still downloading in the background. It'll land on its own.
Already back after the reboot: MongoDB and Core are up, so the database side is ready.
Prep done while waiting: service file and bootstrap script are ready in ldmp-stack/ — port 3250, database ldmp on the local MongoDB, public URL planned as ldmp.mingsea.net. The NEXTAUTH_SECRET generates itself on first start.
One thing I need from you before first start: the admin login. The app checks ADMIN_USER / ADMIN_PASS from the environment, so whatever we set is what you'll type at /login. Want me to generate a strong password (username admin), or will you pick your own?
me: I'll set my own username and password
Got it — your call. Send me the username and password whenever you're ready, and I'll put them in the app's env file only (nothing else, no other copies). No rush: the clone is at 192 MB and still downloading, so the build can't start until it finishes anyway.
me: username: admin pw: 我所设置的密码
Saved — both values are in the app's env file only, placeholders gone, file locked to owner-only access. I won't repeat them anywhere else.
Clone is at 280 MB and still going. Once it lands, I'll install, build, and bring the site up with this login.
Clone finished — 186 files, commit 1d5ec7c. Install, Prisma generate, and the Next build are running in the background now.
Once the build passes, the remaining steps are: start the service on port 3250, point to ldmp.mingsea.net through the tunnel, and verify it live. I'll report back when it's up.
Verified just now: homepage 200, /login 200, and /api/blogs returns an empty list with 200 — so the app, the tunnel, and the MongoDB connection all work.
What it is: the Next 15 personal site with admin backend (blogs, photos, thinkings) and NextAuth login. Log in at /login with the username and password you set. Two things to know:
The site starts empty. I deliberately did not import the upstream author's seed posts (dataScript/*.json) — that's someone else's personal content. You add your own contents through the admin panel.
Admin sessions are short by the template's own setting (10 minutes), so don't be surprised if it asks you to log in again after a while.
The road here was rough (slow 538 MB clone killed twice by VM reboots, pnpm 12 rejecting the old workspace file, Prisma's engine download failing under this proxy) — all worked around locally in this VM clone, nothing pushed to GitHub.
One offer: add ldmp to the 5-minute watchdog, so if a VM reboot wipes its service file again, it restarts automatically.
me: Yes, add ldmp to the watchdog.
It checks that ldmp-app is active and that the site answers locally on port 3250. If either fails, it runs the ldmp bootstrap once, re-checks, and logs the outcome.
me: i don't see where to change the pw after login the blog.
There isn't one — that's why you can't find it. This template doesn't store the password in a database, so the admin has no profile or settings page. Its only pages are the dashboard, Blogs, Photos, and Thinkings.
The login just checks against a password set on the server itself. So to change it, send me the new password (or say "generate one") and I'll swap it in the server config and restart the site. The new one takes effect right away, and you'll need to log in again with it.
Found it — it's a template bug, and it only bites because your blog list is still empty.
The "Create your first blog" button on the empty list links to /admin/blogs/new, but the template never implemented that page. Blog creation actually lives in the "New Blog" dialog on the blog list itself (the header button works — it's the empty-state link that's broken).
Fix going in now: I added the missing /admin/blogs/new page as a redirect into that creation dialog, and pointed the empty-state link straight at it. Rebuilding and will confirm it live.
To create a post now: open Blog Management, hit "Create your first blog" (or "New Blog" at the top), fill in title and description, and it takes you straight into the editor.
One note: this fix lives in the VM copy only, like the other ldmp patches — it isn't pushed to GitHub. Say the word if you want it committed up.
me: and when click '+ new blog', it shows "failed to create blog'. pls fix it.
The handler itself looks fine, but the app log shows repeated prisma:error lines — including one right around your click.
Fixed. The cause was underneath the blog code, not in it:
Your local MongoDB was running as a standalone server, but Prisma runs every write inside a transaction — and MongoDB refuses transactions unless it's a replica set. Reads worked (that's why the empty list loaded fine), but every create failed with a 500, which the UI shows as "Failed to create blog".
I converted MongoDB to a single-node replica set and proved it with a create-and-delete round trip through the same code path the button uses. Nothing was left behind — your two test attempts never actually saved, so the list is still clean at 0 posts.
Try "+ New Blog" again now — it should go through to the editor.
this template's article page renders only the body. Here's the mechanism:
The "New Blog" dialog only asks for title and description. The article text itself lives in a separate markdown file, which starts out empty.
The public page at /blog/<id> fetches just that file and renders it. It never shows the title or description — those only appear on the /blog list.
Your post's body file is currently empty, so the page renders an empty article.
To fill it in: go to Blog Management → Edit on that post → write the article in the editor → Save. Then the public page will show it.
Done building, now checking it live. The pager is in and the site restarted — /blog now shows 5 posts per page with a Previous | 1 | 2 | Next bar, and page 2 holds the 6th post. I'm verifying the rendered pages in your browser right now and will confirm the exact result once that check comes back.
Page 1 shows the 5 newest posts, with a Previous | 1 | 2 | Next bar at the bottom (1 highlighted, Previous greyed out).
Page 2 shows the 6th post (测试), with 2 highlighted and Next greyed out.
The year grouping is kept, just applied per page, and the pager hides itself if you ever drop back to a single page. One note: like the earlier ldmp fixes, this change is in the VM copy only, not pushed to GitHub — say the word if you want it committed up.
me: pls push all the code changes to my repo including the changes above.
Ready to push. Remote is still at the same commit as this clone, so it'll be a clean fast-forward, and no workflow files are touched — a token with Contents read/write on brightmann/ldmp is enough.
Here's everything waiting in the working tree:
src/app/(user)/blog/page.tsx — the pagination from just now
src/app/admin/(auth)/blogs/page.tsx + src/app/admin/(auth)/blogs/new/ — the empty-state "Create your first blog" fix
pnpm-workspace.yaml — the pnpm 12 allowBuilds rewrite (needed to build here)
src/posts/blog/*.md (6 files) — your article bodies, already live on the site; pushing them backs them up in git
Paste a PAT for brightmann/ldmp and I'll commit all of it, push, verify the remote took it, then restore the remote token-free and you can revoke the token.
me: here is the pat....
Staging worked, but the repo's husky pre-commit hook failed — it calls pnpx, which isn't on PATH here. Let me check what the hook actually does before working around it.
Committed as a4733b6 (10 files, tree clean, hook passed). Pushing now.
Pushed and verified. Updating the record to reflect that these are no longer local-only.
Pushed. Commit a4733b6 is now on brightmann/ldmp master (verified the remote HEAD matches), covering all 10 files: the blog pagination, the admin create-link fix, the pnpm 12 workspace rewrite, and your 6 post bodies.
The remote is restored to the plain token-free URL and the working tree is clean. You can revoke that token now.
git clone https://github.com/ManfredMT/nextjs-blog-react-admin.git
cd nextjs-blog-react-admin/admin-blog
npm install
cd ../backend
npm install
cd ../nextjs-blog
npm install
Nightly version is the automatic compile version, that
means, every commit code will be automatically compiled.
The reliability and stability of the data are not guaranteed, you can
deploy with stable version with docker images or github release page
Motivation
At
present, the existing IM applications only focus on chatting itself,
and IM is naturally a multi-person collaboration method. In my opinion,
it should be able to take on more responsibilities, and form its own
unique way of forwarding external applications through IM workflow.
Therefore, I bring up the point of noIM, which means Not only IM.
Instead, it designed a highly customized application platform for
individuals/teams centered on IM, with third-party applications as
enhanced functions, and a plugin system as the glue connection layer in
the middle.
To this end, the functions were abstracted, and a lot of
time was spent designing the underlying mechanism. An instant messaging
application such as Tailchat was born for expansion from the beginning of the underlying design. Through Tailchat's plugin system, developers can easily use their favorite applications as part of Tailchat in a very natural way. Different from traditional integration methods such as Slack, the integration of Tailchat is more free, as if it is a native function.
Feature
Pay attention to privacy, only invited members can join the group
Prevent strangers, add friends only by nickname + a random string of numbers
Two-level group space, dividing different topics by panels
Highly customized group space, create original group space by
grouping with dragging and dropping. At the same time, more plugins can
be used to add more capabilities
It can be rigorous or fun. Through the combination of plugins, Tailchat can be created for different scenarios. It can be for individuals or for enterprises
The backend microservice structure is ready for large-scale
deployment. Don't worry about what to do after the number of user growth
Tailchat is a modern open source IM application which based on React + Typescript
Front-end microkernel architecture + backend microservice architecture, Tailchat is ready for clustering deployment.
The front end empowers the application through the plugin
system, which is very simple and easy to expand for the secondary
development of Tailchat.
NOTICE: Although the core functionality of
Tailchat is currently in a stable stage, its exposed interface for
third-party developers is still being improved. Generally speaking, it
is backward compatible, but retains the possibility of Break Change
The
content of this chapter requires you to have a certain degree of
understanding of nodejs, git, linux. When there are problems such as
dependency problems, environmental problems, system problems, etc., you
need to have the ability to solve and troubleshoot problems by yourself.
If
you do not understand this, it is not recommended that you use the
contents of this chapter for deployment. It is recommended to use a
unified image for deployment.
Because
the cloned code is the latest code, it may be unstable for a short
period of time, so if you want to switch to the stable code of each
version, you can use the tag function of git
For example, if you wanna use v1.7.6, you can use the command:
git checkout v1.7.6
Compile the project
Tailchat
is a front-end and back-end separated project. So we have to deal with
the front-end code and the back-end code separately
Install dependencies
We assume you have installed nodejs v16.18.0+ or above. And installed pnpm v8.3.1 or above
cd tailchat pnpminstall
This
command will take some time to install all the dependencies of
Tailchat. When the installation is complete, the internal plug-in will
automatically execute the compilation command.
Building the project
NODE_ENV=production pnpm build
This
command will execute the commands for compiling the front-end and
back-end management terminals in parallel. And move the front-end
product to the server/dist/public directory of the server.
When the project is built, our product can run normally.
caution:
Please build in macos / linux environment as much as possible, window does not necessarily fully support shell commands.
Run the project
In order to ensure the horizontal expansion of the project, although the core code of Tailchat
is written in the same project, it can be divided into multiple
subdivided microservices when it is actually started. Selectively enable
different services by passing in a combination of different environment
variables.
Create an environment variable file in the server directory using the .env.example directory as an example:
cp server/.env.example server/dist/.env vim .env
Modify the necessary environment variables to your own, such as MONGO_URL, REDIS_URL, MINIO_URL
then start the service
SERVICEDIR=services,plugins pnpm start:service
SERVICEDIR indicates the directory where the microservice is loaded.
from https://tailchat.msgbyte.com/docs/deployment/other-way/manual
DBeaver Community is a free cross-platform database tool for developers, database administrators, analysts, and everyone working with data. It supports all popular SQL databases like MySQL, MariaDB, PostgreSQL, SQLite, Apache Family, and more.
DBeaver Community 是一个 免费 的跨平台 数据库 工具,适用于开发人员、数据库管理员、分析师和所有使用数据的人。它支持所有流行的 SQL 数据库,如 MySQL , MariaDB, PostgreSQL , SQLite , Apache Family 等。dbeaver 它具有如下功能特性:
A web app for writing and running SQL queries and
visualizing the results. Supports Postgres, MySQL, SQL Server,
ClickHouse, Crate, Vertica, Trino, Presto, SAP HANA, Cassandra,
Snowflake, Google BigQuery, SQLite, TiDB and many more via ODBC.
Project Status
SQLPad is a legacy project in maintenance mode. If evaluating SQLPad, please consider a potential alternative or forking the project and making it your own.
Maintenance releases for security and dependency updates will continue as possible.
As of version 7, semver is no longer followed. Going forward patch updates may require major Node.js version updates, or contain removal of functionality.
Some dependencies may require compilation. On macOS, the Xcode Command Line Tools should be installed. On Ubuntu, apt-get install build-essential
will install the required packages. Similar commands should work on
other Linux distros. Windows will require some additional steps, see the
node-gyp installation instructions for details.
Style Guide
SQLPad uses an automatic code formatter called Prettier and a linting tool called ESLint.
Run yarn run lint after making any changes to code to check formatting and lint. Some formatting and lint may be fixed automatically by running yarn run fixlint.
If using Visual Studio Code, Prettier and ESLint
extensions can be installed to assist in detecting and fixing issues
during development.
Getting Started
Clone/download this repo
Install dependencies and build the UI
scripts/build.sh
The gist of this script is:
# install root level dependencies using package-lock.json as reference
yarn
# install front-end dependencies using package-lock.jsoncd client
yarn
# build front-end
yarn build
# install back-end dependenciescd ../server
yarn
cd ..
# copy client build to server directory
mkdir server/public
cp -r client/build/* server/public
At this point you can run the SQLPad server with the front-end built for production use:
cd server
node server.js --config ./config.dev.env
If preferred, SQLPad can be installed as a
global module using the local files in this repo. This allows running
SQLPad via the cli in any directory, just as if you had installed it
with npm install sqlpad -g. Note that you must build and copy the client prior to this step.
cd server
npm install -g
# Now from somewhere else you can run sqlpad likecd~
sqlpad --config ./config.dev.env
If sqlpad was installed globally via npm from npm, you may need to run npm uninstall sqlpad -g.
A docker image may be built using the Dockerfile located in server directory. See docker-publish.sh for example docker build command.
Developing
Open 2 terminal sessions in the root of this repo.
In one session run the back end in development mode
cd server
yarn start
In the other start the development server for the front end.
cd client
yarn start
At this point you should have both back end and front end development servers running.
When viewing the front end in development mode, the page
will automatically refresh on client file changes. The back end server
will auto-restart on back end file changes as well.
When viewing SQLPad in dev-mode in port 3000, some
features may not work correctly (like csv/xlsx downloads, google auth).
This is likely due to the port difference in configuration (google auth
can only redirect to 1 url/port) or the dev-mode proxy setup (React dev
mode is served by a secondary web server that will proxy requests it
doesn't understand to the SQLPad server running on 3010 during
development.)
ESLint and Prettier are used to enforce code patterns and
formatting in this project. A precommit hook should enforce and warn
about these checks. If that is not set up however you may find these
terminal commands useful.
# To check lint
yarn run lint
# To fix (some) errors and formatting automatically
yarn run fixlint
Developing on Windows
To run build/scripts.sh on Windows, you may want to use an application like cmder. It will allow you to run scripts/build.sh by calling sh directly with sh scripts/build.sh.
Test/Dev Database Connection
A Node.js script, server/generate-test-db-fixture.js,
can be used to generate a test sqlite database to be used for tests and
local development. This replaces the previous mock driver
implementation that was enabled when the debug flag was turned on.
This test database allows for running SQL you likely know,
instead of having to remember and use some variables set in SQL
comments.
The script adds a sqlite database under server/test/fixtures/sales.sqlite.
It can be used within SQLPad by creating a connection using the SQLite driver, and setting the filename to ./test/fixtures/sales.sqlite.
The data in the database is somewhat nonsensical. It is
also not randomized so that the results can be predictable. If you'd
like to expand on this database, feel free.
Running Tests
SQLPad's test cases focus on the API server, with majority
of tests being integration tests, with some unit tests sprinkled
throughout.
Tests are located under server/test directory, and use mocha as a test runner. Tests may be run by running yarn test
within the server directory. For tests to run successfully,
dependencies must be installed and the test database fixture generated.
cd server
# if dependencies have not yet been installed (build.sh will do this)
yarn
# If test fixture has not yet been generated (build.sh will do this)
node generate-test-db-fixture.js
# Start backend services if desired. (-d runs in background)
docker-compose up -d redis
docker-compose up -d ldap
# Run tests
yarn test# If you are aiming to run a specific test case,# you may do so using npx to call mocha,# specifying the path to the test file and --exit to exit after tests have run
npx mocha test/path/to/file.js --exit
from https://github.com/sqlpad/sqlpad/blob/master/DEVELOPER-GUIDE.md)
(Getting Started
Running SQLPad
Building from source
SQLPad does not require any additional servers other than its own
self. By default it uses SQLite and the file system for storing queries,
query results, and web sessions. SQLite may be replaced with an
external database. See backend database configuration for more info.
gh-ost是一款支持在线更改 MySQL 表结构的开源工具,遵守MIT开源协议。gh-ost无触发器,可监控,可动态调整暂停,实现新旧表切换的(cut-over)顺畅。 三种工作模式:1:连接到从库,在主库做迁移。2:连接到主库,迁移过程所有操作都在主上操作,包括读取binlog等等。3:在从库做迁移测试。
VS Code已经有一个SQL扩展(vscode-mssql),但微软的SQL Server Management Studio只能运行在Windows上。SQL Operation Studio 能够和 VS Code 深度集成,运行在不同操作系统上。重要特性包括:T-SQL编辑器,支持自动完成和错误检查,可将结果导出到CSV或Excel,还支持直接手动插入、修改、删除表记录。SqlOps还集成了一个对象浏览器,开发者可以通过它查看SQL Server和表信息、视图、存储过程等 。
Presto is a distributed SQL query engine for big data.
See the User Manual for deployment instructions and end user documentation.
Requirements
Mac OS X or Linux
Java 8 Update 151 or higher (8u151+), 64-bit. Both Oracle JDK and OpenJDK are supported.
Maven 3.3.9+ (for building)
Python 2.4+ (for running with the launcher script)
Building Presto
Presto is a standard Maven project. Simply run the following command from the project root directory:
./mvnw clean install
On the first build, Maven will download all the dependencies from the internet and cache them in the local repository (~/.m2/repository), which can take a considerable amount of time. Subsequent builds will be faster.
Presto has a comprehensive set of unit tests that can take several minutes to run. You can disable the tests when building:
After building Presto for the first time, you can load the project into your IDE and run the server. We recommend using IntelliJ IDEA. Because Presto is a standard Maven project, you can import it into your IDE using the root pom.xml file. In IntelliJ, choose Open Project from the Quick Start box or choose Open from the File menu and select the root pom.xml file.
After opening the project in IntelliJ, double check that the Java SDK is properly configured for the project:
Open the File menu and select Project Structure
In the SDKs section, ensure that a 1.8 JDK is selected (create one if none exist)
In the Project section, ensure the Project language level is set to 8.0 as Presto makes use of several Java 8 language features
Presto comes with sample configuration that should work
out-of-the-box for development. Use the following options to create a
run configuration:
Main Class: com.facebook.presto.server.PrestoServer
VM Options: -ea -XX:+UseG1GC -XX:G1HeapRegionSize=32M -XX:+UseGCOverheadLimit -XX:+ExplicitGCInvokesConcurrent -Xmx2G -Dconfig=etc/config.properties -Dlog.levels-file=etc/log.properties
Working directory: $MODULE_WORKING_DIR$ or $MODULE_DIR$(Depends your version of IntelliJ)
Use classpath of module: presto-main
The working directory should be the presto-main subdirectory. In IntelliJ, using $MODULE_DIR$ accomplishes this automatically.
Additionally, the Hive plugin must be configured with
location of your Hive metastore Thrift service. Add the following to the
list of VM options, replacing localhost:9083 with the correct host and port (or use the below value if you do not have a Hive metastore):