免费酒店管理系统+餐饮系统+小程序点餐—

酒店系统主屏幕

房间管理

酒店管理系统的房间管理，可实现对酒店所有房间的实时掌控。它能清晰显示房间状态，如已预订、已入住、空闲等，便于高效安排入住与退房，合理分配资源，提升服务效率，保障酒店运营有条不紊

房型管理

酒店管理系统的房型管理至关重要。它能清晰划分各类房型，如单人间、套房等，实时掌握各房型数量与状态。助酒店合理定价，优化资源配置，精准满足不同客人需求，提升入住体验与酒店运营效率

楼层管理

酒店管理系统的楼层管理，对酒店有序运营意义重大。它能按楼层整合房间信息，便于员工快速定位。通过合理规划各楼层功能，优化房间分配，提升客人入住便捷性，同时助力酒店进行针对性维护与管理

促销管理

订单管理

酒店管理系统中的订单管理，对酒店运营起着核心枢纽作用。它整合来自各渠道的订单，实时更新客房预订状态，避免超售。能精准记录客人信息、入住退房时间及特殊需求，助酒店提供个性化服务。通过分析订单数据，还能预测客源趋势，辅助房价与营销策略制定。

而早餐管理是其贴心延伸。可依订单统计含早人数，便于厨房备餐，减少浪费。系统还支持客人提前选择早餐类型，优化就餐流程。同时记录客人饮食偏好，为后续服务提供参考，全方位提升客人住宿体验，增强酒店竞争力。

餐饮管理

酒店管理系统的餐饮管理点菜功能，为酒店餐饮服务带来高效与便捷。顾客可通过线上平台、酒店内平板等终端便捷点菜，系统实时将订单传送至厨房，减少沟通误差与服务时间。

工作人员能借助该功能，清晰查看菜品库存，避免点单后无货的尴尬情况，及时调整采购计划。同时，系统记录顾客点菜偏好与历史订单，方便提供个性化推荐，提升顾客用餐体验。此外，它还能统计菜品销量，助力酒店分析热门菜品，优化菜单结构，提高餐饮运营效益。

酒店宣传-智慧大屏幕

系统安装方法

1.安装环境

npm install

2.运行酒店系统

npm run dev

3.安装数据库

安装mysql，自行安装mysql

https://www.mysql.com/cn/

4. 安装缓存

redis

安装下载地址：https://github.com/bpollack/miniredis

启动

系统配置截图

redis 文件截图

安装环境截图

redis运行图

常见错误

无redis

配置信息

1.red配置


# Include one or more other config files here.  This is useful if you
# have a standard template that goes to all Redis servers but also need
# to customize a few per-server settings.  Include files can include
# other files, so use this wisely.
#
# Note that option "include" won't be rewritten by command "CONFIG REWRITE"
# from admin or Redis Sentinel. Since Redis always uses the last processed
# line as value of a configuration directive, you'd better put includes
# at the beginning of this file to avoid overwriting config change at runtime.
#
# If instead you are interested in using includes to override configuration
# options, it is better to use include as the last line.
#
# Included paths may contain wildcards. All files matching the wildcards will
# be included in alphabetical order.
# Note that if an include path contains a wildcards but no files match it when
# the server is started, the include statement will be ignored and no error will
# be emitted.  It is safe, therefore, to include wildcard files from empty
# directories.
#
# include /path/to/local.conf
# include /path/to/other.conf
# include /path/to/fragments/*.conf
################################### MODULES ###################################### Load modules at startup. If the server is not able to load modules
# it will abort. It is possible to use multiple loadmodule directives.
#
# loadmodule /path/to/my_module.so
# loadmodule /path/to/other_module.so
# loadmodule /path/to/args_module.so [arg [arg ...]]################################## NETWORK ###################################### By default, if no "bind" configuration directive is specified, Redis listens
# for connections from all available network interfaces on the host machine.
# It is possible to listen to just one or multiple selected interfaces using
# the "bind" configuration directive, followed by one or more IP addresses.
# Each address can be prefixed by "-", which means that redis will not fail to
# start if the address is not available. Being not available only refers to
# addresses that does not correspond to any network interface. Addresses that
# are already in use will always fail, and unsupported protocols will always BE
# silently skipped.
#
# Examples:
#
# bind 192.168.1.100 10.0.0.1     # listens on two specific IPv4 addresses
# bind 127.0.0.1 ::1              # listens on loopback IPv4 and IPv6
# bind * -::*                     # like the default, all available interfaces
#
# ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
# internet, binding to all the interfaces is dangerous and will expose the
# instance to everybody on the internet. So by default we uncomment the
# following bind directive, that will force Redis to listen only on the
# IPv4 and IPv6 (if available) loopback interface addresses (this means Redis
# will only be able to accept client connections from the same host that it is
# running on).
#
# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
# COMMENT OUT THE FOLLOWING LINE.
#
# You will also need to set a password unless you explicitly disable protected
# mode.
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bind 127.0.0.1 -::1# By default, outgoing connections (from replica to master, from Sentinel to
# instances, cluster bus, etc.) are not bound to a specific local address. In
# most cases, this means the operating system will handle that based on routing
# and the interface through which the connection goes out.
#
# Using bind-source-addr it is possible to configure a specific address to bind
# to, which may also affect how the connection gets routed.
#
# Example:
#
# bind-source-addr 10.0.0.1# Protected mode is a layer of security protection, in order to avoid that
# Redis instances left open on the internet are accessed and exploited.
#
# When protected mode is on and the default user has no password, the server
# only accepts local connections from the IPv4 address (127.0.0.1), IPv6 address
# (::1) or Unix domain sockets.
#
# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured.
protected-mode yes# Redis uses default hardened security configuration directives to reduce the
# attack surface on innocent users. Therefore, several sensitive configuration
# directives are immutable, and some potentially-dangerous commands are blocked.
#
# Configuration directives that control files that Redis writes to (e.g., 'dir'
# and 'dbfilename') and that aren't usually modified during runtime
# are protected by making them immutable.
#
# Commands that can increase the attack surface of Redis and that aren't usually
# called by users are blocked by default.
#
# These can be exposed to either all connections or just local ones by setting
# each of the configs listed below to either of these values:
#
# no    - Block for any connection (remain immutable)
# yes   - Allow for any connection (no protection)
# local - Allow only for local connections. Ones originating from the
#         IPv4 address (127.0.0.1), IPv6 address (::1) or Unix domain sockets.
#
# enable-protected-configs no
# enable-debug-command no
# enable-module-command no# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
#port 6379
port 20259# TCP listen() backlog.

配置命令

npm install
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated @humanwhocodes/config-array@0.5.0: Use @eslint/config-array instead
npm warn deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated @stylelint/postcss-markdown@0.36.2: Use the original unforked package instead: postcss-markdown
npm warn deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.1.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm warn deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm warn deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm warn deprecated @humanwhocodes/object-schema@1.2.1: Use @eslint/object-schema instead
npm warn deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm warn deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated @stylelint/postcss-css-in-js@0.37.3: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm warn deprecated superagent@3.8.3: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net
npm warn deprecated eslint@5.16.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated eslint@7.32.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.added 1918 packages, and audited 2056 packages in 11m229 packages are looking for fundingrun `npm fund` for details94 vulnerabilities (5 low, 22 moderate, 23 high, 44 critical)To address issues that do not require attention, run:npm audit fixTo address all issues (including breaking changes), run:npm audit fix --forceRun `npm audit` for details.D:\ai\wlzchotelfree>npm run dev> hotel-manage@1.0.0 dev
> egg-bin dev --sticky[egg-ts-helper] create typings\app\extend\application.d.ts (17ms)
[egg-ts-helper] create typings\app\extend\context.d.ts (19ms)
[egg-ts-helper] create typings\app\extend\helper.d.ts (24ms)
[egg-ts-helper] create typings\app\controller\index.d.ts (80ms)
[egg-ts-helper] create typings\app\middleware\index.d.ts (18ms)
[egg-ts-helper] create typings\app\model\index.d.ts (19ms)
[egg-ts-helper] create typings\config\index.d.ts (38ms)
[egg-ts-helper] create typings\config\plugin.d.ts (23ms)
[egg-ts-helper] create typings\app\service\index.d.ts (42ms)
[egg-ts-helper] create typings\app\index.d.ts (2ms)
2025-06-02 02:37:39,637 INFO 15384 [master] node version v22.13.0
2025-06-02 02:37:39,639 INFO 15384 [master] egg version 2.37.0
[egg-ts-helper] create typings\app\extend\application.d.ts (6ms)
[egg-ts-helper] create typings\app\extend\context.d.ts (9ms)
[egg-ts-helper] create typings\app\extend\helper.d.ts (11ms)
[egg-ts-helper] create typings\app\controller\index.d.ts (12ms)
[egg-ts-helper] create typings\app\middleware\index.d.ts (5ms)
[egg-ts-helper] create typings\app\model\index.d.ts (7ms)
[egg-ts-helper] create typings\config\index.d.ts (41ms)
[egg-ts-helper] create typings\config\plugin.d.ts (3ms)
[egg-ts-helper] create typings\app\service\index.d.ts (9ms)
[egg-ts-helper] create typings\app\index.d.ts (3ms)
Ignoring invalid timezone passed to Connection: +8:00. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
2025-06-02 02:37:52,388 ERROR 13564 [egg-redis] client error: Error: connect ECONNREFUSED 127.0.0.1:6379at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16) {errno: -4078,code: 'ECONNREFUSED',syscall: 'connect',address: '127.0.0.1',port: 6379
}
2025-06-02 02:37:52,391 ERROR 13564 nodejs.ECONNREFUSEDError: connect ECONNREFUSED 127.0.0.1:6379at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16)
errno: -4078
code: "ECONNREFUSED"

阿雪技术观

让我们积极投身于技术共享的浪潮中，不仅仅是作为受益者，更要成为贡献者。无论是分享自己的代码、撰写技术博客，还是参与开源项目的维护和改进，每一个小小的举动都可能成为推动技术进步的巨大力量

Embrace open source and sharing, witness the miracle of technological progress, and enjoy the happy times of humanity! Let's actively join the wave of technology sharing. Not only as beneficiaries, but also as contributors. Whether sharing our own code, writing technical blogs, or participating in the maintenance and improvement of open source projects, every small action may become a huge force driving technological progress.